From: Keith Whitwell <keith@tungstengraphics.com>
To: Arjan van de Ven <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 11:12:53 +0100 [thread overview]
Message-ID: <412088A5.6010106@tungstengraphics.com> (raw)
In-Reply-To: <20040816094622.GA31696@devserv.devel.redhat.com>
Arjan van de Ven wrote:
> On Mon, Aug 16, 2004 at 10:43:34AM +0100, Keith Whitwell wrote:
>
>>If we can manage to support FreeBSD and Linux from one codebase, surely
>>supporting 2.4 and 2.6 isn't too difficult?
>
>
> It for sure is possible.
> However the DRM codebase proves that it's incapable of even doing BSD
> support properly (eg without the right abstractions but instead fouling up
> the entire codebase to the point of unreadability). That gives me no
> confidence the "keep 2.4 support" will not turn out to be at least as
> ugly/broken/wrong.
Well... I think there's some confusion regarding how much of the macro-itis
in the current DRM is related to support for freebsd and how much is just a
reasonable idea taken too far.
Most of the abstractions that you're complaining about existed prior to the
addition of freebsd support, and right now, Dave Airlie is doing good work
returning the codebase to something less obscure.
Anyway, as far as I'm concerned 2.4 support is of primary importance to the
people who actually use this code, so I will work to see it retained.
Keith
next prev parent reply other threads:[~2004-08-16 10:15 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
2004-08-16 9:46 ` Arjan van de Ven
2004-08-16 10:12 ` Keith Whitwell [this message]
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=412088A5.6010106@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