I had indicated an interest in implementing the DCT and motion estimation on the shader units to provide hardware acceleration of MPEG video some time back. I have been far too busy and haven't even done any background work whatsoever to learn about the shader units. I presume this is still up in the air and that there is no serious effort yet to implement such features, right?
There's been some work to implement video decode acceleration in mesa via gallium. In that case, video decode acceleration would just work on any gallium driver. Currently the r300 gallium driver (for r3xx-r5xx radeons) is fairly far along, but the r600 one has barely started; mostly just some experiments. The advantage of gallium is that new front ends can be added to support acceleration of new APIs without requiring a new driver for each one. There is already work to support OpenGL, OpenCL, OpenVG, EXA, and video decode on top of gallium. I played around a bit with the XvMC gallium state tracker, but only with
Am Montag, den 25.01.2010, 16:12 -0500 schrieb Alex Deucher: the software rendering stack and just to learn a little bit about the design. IDCT and MC should be pretty easy, IDCT are just a bunch of cos and mul operations, and MC scripted blitter operations. The real tricky part is VLD, i have no clue how this works. Just leave me a note if you got something interesting to test or could explain how VLD works. Bye, Christian. -- To unsubscribe, e-mail: radeonhd+unsubscribe@opensuse.org For additional commands, e-mail: radeonhd+help@opensuse.org