public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Keith Whitwell <keith@tungstengraphics.com>
To: arjanv@redhat.com
Cc: Dave Airlie <airlied@linux.ie>,
	dri-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: DRM and 2.4 ...
Date: Mon, 16 Aug 2004 10:43:34 +0100	[thread overview]
Message-ID: <412081C6.20601@tungstengraphics.com> (raw)
In-Reply-To: <1092640312.2791.6.camel@laptop.fenrus.com>

Arjan van de Ven wrote:
> On Mon, 2004-08-16 at 07:56, Dave Airlie wrote:
> 
>>At the moment we are adding a lot of 2.6 stuff to the DRM under
>>development in the DRM CVS tree and what will be merged into the -mm and
>>Linus trees eventually, this has meant ifdefing stuff out so 2.4 will
>>still work,
> 
> 
> which is uglyfying the code significantly if done wrong
> 
> 
>>So the question is do we want to a final stable DRM for 2.4 in the next
>>2.4 release? and after that point I can tag the 2.4 release in the DRM CVS
>>tree (and maybe branch it ...),
> 
> 
> I would strongly urge you to no longer update DRM in 2.4 in significant
> ways. 2.4 is the release for doing strict maintenance; people who want
> to run newer X will generally run 2.6 kernels as well anyway.

I'm not at all convinced we (ie the DRI project) can abandon 2.4 support.  In 
fact we made this mistake with the 2.2/2.4 transition - we didn't support 2.2 
at all, only 2.4 and for a long time this was a big inconvenience to users.

We may not be feeding our changes into the 2.4 kernel (or maybe we are), but I 
definitely view 2.4 support as important for probably 1 to 2 years to come.

If we can manage to support FreeBSD and Linux from one codebase, surely 
supporting 2.4 and 2.6 isn't too difficult?

Keith


  reply	other threads:[~2004-08-16  9:43 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-16  5:56 DRM and 2.4 Dave Airlie
2004-08-16  7:11 ` Arjan van de Ven
2004-08-16  9:43   ` Keith Whitwell [this message]
2004-08-16  9:46     ` Arjan van de Ven
2004-08-16 10:12       ` Keith Whitwell
2004-08-16 10:14         ` Arjan van de Ven
2004-08-16 10:42           ` Dave Airlie
2004-08-16 10:48             ` Arjan van de Ven
2004-08-16 11:42             ` Keith Whitwell
2004-08-16 11:58               ` Arjan van de Ven
2004-08-16 12:18                 ` Keith Whitwell
2004-08-16 11:14   ` Alan Cox
2004-08-16 12:22     ` Dave Airlie

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=412081C6.20601@tungstengraphics.com \
    --to=keith@tungstengraphics.com \
    --cc=airlied@linux.ie \
    --cc=arjanv@redhat.com \
    --cc=dri-devel@lists.sourceforge.net \
    --cc=linux-kernel@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