I'm rearranging the xlib code in a side-branch off gallium-0.2.  

The point of this (as well as general cleanup) as an experiment in
splitting out some of the remaining chunks of device-independent code
we're carrying around in the winsys's.  

To this end, I've lifted a chunk of code into a new state_trackers/xlib
directory.  This code is a state_tracker for the GLX api.

There are actually quite a few drivers that have been piggy-backing on
the xlib GLX code -- softpipe and cell in particular, but it's also a
great way to host debug drivers that emit command dumps but which
haven't yet been hooked up to any sort of working kernel module.

Right now, I've tested glxgears on softpipe under the new code
organization, and not much more.  It would be good if a Cell person
could take a look & see how much I've broken that driver.

I'm also hoping to strip out some of the accumulated cruft in the Xlib
support & get the code back down to something a little more focussed.

Keith


------------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It is the best place to buy or sell services for
just about anything Open Source.
http://p.sf.net/sfu/Xq1LFB
_______________________________________________
Mesa3d-dev mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mesa3d-dev

Reply via email to