I should probably make it clear that the public repos already contain display / modesetting code and the kernel driver portion of the acceleration code.
What we're missing right now is the userspace portion of the acceleration code... we're trying to do things in a different sequence this time to shorten the delay between "having support available" and "having support available in a distro" and to reduce duplicated effort between X and 3D drivers.
I suppose that a very important question is WHO should we be complaining TO?
** especially to get new and highly wanted features in open source?
We know that obviously YOU are aware of what we want, so who do we complain to who can tell you that it is now time to make it happen yesterday?
If it's an open source feature, complain to me.
If it's something in the proprietary driver then it's not so easy, you basically need to complain back up the channels you are buying from, or just ignore the fact that you were given a lot of advance warning by Phoronix and wait for us to actually finish development![]()
EDIT:
Actually, I'm working on a vdpau backend for gallium right now. Its close beeing able to decode mpeg2, but thats only for the softpipe. R300 should theoreticfally work too, but is untested by me. The video-pipe I am using, is AFAIK already working with the xvmc state-tracker. I am just also implementing it as a vdpau state-tracker.
Sounds like buying beer for tball might be the smart move![]()