From: Gareth Hughes <gareth.hughes@acm.org>
To: linux-kernel@vger.kernel.org
Subject: Re: Linux 2.4.6-ac3
Date: Mon, 16 Jul 2001 00:01:19 +1000 [thread overview]
Message-ID: <3B51A22F.16C6FEBB@acm.org> (raw)
In-Reply-To: <E15Llhc-0003zS-00@the-village.bc.nu>
Alan Cox wrote:
>
> DRM 4.1 is something that needs discussion rather than being ignored. I sort
> of expect it to look like XFree code anyway and I can see bits of the macro
> stuff will really help with the *BSD code
Some of the discussions I've had with various people regarding the DRM
make me think people miss how tightly coupled the 3 parts of a full DRI
driver are (the other two parts being the XFree86 2D driver and the
client-side 3D driver). It's not like the various interfaces between
the 3 parts are changed for the fun of it. Granted, issues of backwards
compatibility haven't been handled well in the past, but with the next
resync I believe that moving forward this will no longer be a problem.
You'd have to talk to the guys at VA about this, however.
Portability and maintainability were certainly two motivating factors in
the move to a templated architecture for the core DRM. I just got sick
of seeing the same code in every driver -- kinda defeats the purpose of
having a "core" DRM if it isn't being used... New drivers are much
easier to write as well, which is a nice side-effect.
-- Gareth
next prev parent reply other threads:[~2001-07-15 14:01 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-14 17:36 Linux 2.4.6-ac3 Alan Cox
2001-07-14 20:01 ` Zilvinas Valinskas
2001-07-14 20:05 ` Alan Cox
2001-07-15 1:45 ` Gareth Hughes
2001-07-15 13:12 ` Alan Cox
2001-07-15 14:01 ` Gareth Hughes [this message]
2001-07-15 15:31 ` Alan Cox
2001-07-16 1:29 ` 4.1.0 DRM (was Re: Linux 2.4.6-ac3) Gareth Hughes
2001-07-16 1:51 ` Keith Owens
2001-07-16 2:07 ` Gareth Hughes
2001-07-16 11:23 ` John Cavan
2001-07-16 11:39 ` Alan Cox
2001-07-16 18:00 ` Jeff Hartmann
2001-07-16 18:12 ` Xavier Bestel
2001-07-16 18:32 ` Jeff Hartmann
2001-07-16 18:42 ` John Cavan
2001-07-16 19:32 ` Jeff Hartmann
2001-07-16 19:34 ` Xavier Bestel
2001-07-16 20:18 ` Jeff Hartmann
2001-07-17 2:37 ` Gareth Hughes
2001-07-17 8:31 ` Mike A. Harris
2001-07-16 19:49 ` John Cavan
2001-07-17 7:19 ` 4.1.0 DRM Mike A. Harris
2001-07-17 5:28 ` 4.1.0 DRM (was Re: Linux 2.4.6-ac3) Juan Quintela
2001-07-18 9:06 ` Gareth Hughes
2001-07-18 16:21 ` Juan Quintela
2001-07-18 13:30 ` Mike A. Harris
2001-07-17 13:19 ` Linux 2.4.6-ac3 Zdenek Kabelac
2001-07-15 1:31 ` Linux 2.4.6-ac3 - some unresolved Eyal Lebedinsky
2001-07-15 13:09 ` Alan Cox
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=3B51A22F.16C6FEBB@acm.org \
--to=gareth.hughes@acm.org \
--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