So, somebody pointed out that the TG page on Gallium is a bit dated. While this is true, it's still got a lot of writing, and a lot of theory. So, in order to get the status condensed down into a nice, easy-to-grok format, I decided to pull out my special technique, the STATUS MATRIX.
http://www.x.org/wiki/GalliumStatus is the location. (Could have done it on dri.freedesktop.org, but this really isn't DRI-specific anymore.) So, here's a few things to note. First, you'll note that nothing's marked as DONE. This is because, frankly, I felt like trying to embarrass us all, myself included, into defining serious conformance tests for state trackers. In the process, hopefully we can get some clarification and docs on how each of these st works. The obvious first target is mesa st; I suggest we adopt either piglit or glean as a conformance test, and get softpipe to pass. Then, in order for a pipe driver to pass, it must meet or surpass softpipe. (Of course, this is assuming softpipe still doesn't pass piglit; I haven't checked in a loooong time.) The idea is that, with a bit of time, we can start to pare down the st set into something coherent. Not many of the st fully adhere to the ideal of one st, one driver, one winsys, and while I know that's not ever going to be possible, it might be nice to make more progress towards a uniform setup. Suggestions, flames, comments? Do any of the maintainers of the other drivers want to speak up on the status of their code? ~ C. ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ Mesa3d-dev mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mesa3d-dev
