Stephane Marchesin wrote: > On Thu, Apr 9, 2009 at 17:18, Alex Deucher <alexdeuc...@gmail.com> wrote: >> FWIW, MC is done using the 3D engine on our hardware, so MC should be >> able to be implemented now for those that are interested. r3xx+ use >> shaders. r1xx/r2xx have a couple special bits to flip in the 3D >> engine. idct is handled by a separate block what we hope to >> eventually release either code or docs for. >> > > For r100/r200 a specific implementation is going to be your only > option, but let's be honest, those cards can't do H.264. And these > days you can to H.262/263 just fine on the CPU anyway... > > That's my point: video codecs move too fast to be put into silicon, > and require too many resources to implement. So we should use shaders > and lay everything onto an API that takes care of the hardware > details.
This++. ~ C. ------------------------------------------------------------------------------ This SF.net email is sponsored by: High Quality Requirements in a Collaborative Environment. Download a free trial of Rational Requirements Composer Now! http://p.sf.net/sfu/www-ibm-com _______________________________________________ Mesa3d-dev mailing list Mesa3d-dev@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mesa3d-dev
