Sven Luther wrote:
On Thu, Dec 12, 2002 at 07:14:45PM -0800, Philip Brown wrote:

On Thu, Dec 12, 2002 at 01:02:30PM +0000, Alan Cox wrote:

...
It takes two to tango so its not just what I need its also what do they
need.

What I would like to see would be:

A single definitive source for the DRM code, one where contributions go
back from Linux, from *BSD, from core XFree86 as well as from the DRI
project.

May I suggest that the best way to do that, is to keep the kernel DRM code,
as a **SEPARATE PROJECT**, at least on the source code repository level.

IMO, there should be a separate repository, or at least a separate
directory at the same level as the top-level "xc".

The only thing from the driver that really belongs buried in the xfree86
server code, is a single, os-neutral copy of "drm.h", from whatever version
of DRM that branch of xfree86 is officially supporting.


Once you have achieved that separation, you have something actually
resembling a formal API between user-level and kernel driver level.
That is the only way things are going to get cleaned up, process-wise.
Not to mention greatly aiding kernel coding efforts for non-linux
platforms.

And there are also people wanting to use the DRM outside of XFree86,
maybe even outside of the DRI, not sure though.
This is true: I'm working (in Mesa CVS, atm) on an embedded radeon 3d driver that lives on top of fbdev, for instance. (There was the fb_dri project that achieved similar goals, but not very cleanly).

It's clear that both the drm and the 3d clientside drivers have a life outside XFree86, but what isn't clear is how to express this in a reasonable development environment or set of CVS trees.

Keith




-------------------------------------------------------
This sf.net email is sponsored by:
With Great Power, Comes Great Responsibility Learn to use your power at OSDN's High Performance Computing Channel
http://hpc.devchannel.org/
_______________________________________________
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel

Reply via email to