I fail to understand. Did you mistake me with duby229? Or should I have prefaced my post with "CAUTION: IRONY" ?
About not liking something, and/or not liking the general direction of things, and then coding up how they should be... I have done that many times before. And several of those have turned out to be real winners, even though the people who get proven wrong in such a case, are usually not very sportive about it. This means that credit is then not given where credit is due, and this is where the whole meritocracy thing breaks down, as the next time round, the same story has to be played all over again, in pretty much the same way, with a sizable waste of resources as a consequence.
About ctrl-alt-bcksp... I miss that too (i know, it's only off per default). It's like the X stipple and the VGA text console. When you see the stipple, you know that your driver code is not horribly broken. When it is horribly broken, you might still have ctrl-alt-backspace, which then hopefully gives you the VGA console again. If you see the VGA console again, you get to play again... All 3 are happily tied together for a graphics driver developer :)
For X server 1.9, the tentative plan is to merge the device-dependent drivers back into the X server.
Your work here on Mesa seems to be doing the opposite.
So, do you disagree with the move to merge the DDXs into the X server? If so, please explain.
If not, how is the situation with DDX/X server sufficiently different from Mesa to warrant this move in the opposite direction?
Ask yourself, what good does this move bring that isn't already fully provided for by the tinderbox?
The graphics driver developers who want this just want to be lazy, and just want to be more free to break the APIs in a bad and untrackable way.
People believe that the kernel model works for hardware as complicated and volatile as graphics hardware, but time will tell differently.
I am still working on a README, and will make more noise once i have had some shut-eye.
For the adventurous, here is the quick summary:
* pick versions that are very close to your current mesa version (libGL needs to match)
> ./autogen.sh [maybe want to add --prefix=/usr/]
> make dri-sdk
> make dri-sdk-install
Then you can build, install and run your dri driver.