From: David Mosberger <davidm@hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] Linux 2.4.17-pre6 drm-4.0
Date: Fri, 07 Dec 2001 23:38:23 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590698805656@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590698805653@msgid-missing>
>>>>> On Sat, 08 Dec 2001 10:20:10 +1100, Keith Owens <kaos@ocs.com.au> said:
Keith> On Fri, 7 Dec 2001 19:38:23 -0200 (BRST), Marcelo Tosatti
Keith> <marcelo@conectiva.com.br> wrote:
>> pre6: - direct render for some SiS cards (Torsten Duwe/Alan Cox)
Keith> IA64 is still using the drm-4.0 code, as are the (possibly
Keith> obsolete) -ac kernels. The drm 4.0 makefiles are a pain in
Keith> the neck and I want to get rid of them asap. The SiS direct
Keith> render is only for drm 4.1 so now is a good time to question
Keith> if 4.0 is still required.
Keith> How long do people plan to keep drm 4.0 code in their
Keith> versions of the kernel?
You mean for 2.5? I don't think there is a good reason to keep
drm-4.0 there. For 2.4, we should keep it because there might be
folks out there that rely on it.
--david
next prev parent reply other threads:[~2001-12-07 23:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-07 23:20 [Linux-ia64] Linux 2.4.17-pre6 drm-4.0 Keith Owens
2001-12-07 23:38 ` David Mosberger [this message]
2001-12-08 0:25 ` Keith Owens
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=marc-linux-ia64-105590698805656@msgid-missing \
--to=davidm@hpl.hp.com \
--cc=linux-ia64@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox