Alex Deucher wrote:
Currently all my mergedfb work has been in the 2D driver, but I'd like
to start working on some 3d stuff (time permitting).  however, I don't
have write access to the mesa tree.  It's not real important at this
point I guess, but eventually...  Also isn't mesa hosted on
sourceforge?  will there be issues with cvs access (not that
freedesktop is perfect)? will it all be in one mesa tree or will the
DRI have it's own copy in our cvs?  Just curious...

A lot of these are open questions.


The DRI tree could be set up so that it points to a Mesa tree which can be used to track Mesa cvs directly. I'm not sure whether that will be helpful or necessary, though it would make sense for the snapshots to be built this way.

We could set up the DRI tree to have *some* version of Mesa plus drivers installed actually in the tree. One problem with this is it possibly extends the chain to the user - Mesa->DRI->Xfree86->Distro->user... (Actually Mesa updates have to go through this route already) Ideally I'd like to see something closer to Mesa->Distro->user, allowing driver updates to make it into general users hands a lot quicker. We do have snapshots, but the distros are still the main way of getting code into users hands, and we should try & streamline that path.

It's necessary to ask 'what is the DRI tree for?' - what are we still developing there? There is your 2d work, which is somewhat of an exception, but also
- libGL.so
- The DRI protocol.
- The dri & glx XFree86 modules
- The DRI-aware parts of the DDX drivers.


I'm not sure how easy it will be to get updates into XFree86 compared to the past when regular merges took place. This could mean that the DRI tree either becomes more or less important over time...

Keith



-------------------------------------------------------
This SF.Net email sponsored by: ApacheCon 2003,
16-19 November in Las Vegas. Learn firsthand the latest
developments in Apache, PHP, Perl, XML, Java, MySQL,
WebDAV, and more! http://www.apachecon.com/
_______________________________________________
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel

Reply via email to