2009/4/9 Zou, Nanhai <nanhai....@intel.com>: > > You can choose to implement 1 single entry point e.g. VLD. > What I think VAAPI is missing is post processing,However I can talk to > VAAPI people to improve the API, anyway VAAPI is only at version 0.30. > >> >>> I think merge the VAAPI support into mesa might be a good idea. >> >>If you don't have gallium for your chip, you have a specific >>implementation then? In which case it doesn't make much sense to merge >>it into mesa... >> > > > Our current XVMC-vld implementation is in the 2D driver. > > I am planning to implement to support VAAPI in a stand alone liberary. > However I am thinking implement VAAPI in mesa may help us to have less > duplicated code, That means support for dri stuff, rendering, multi stream > blending , scaling, subpicture easier. >
Hmm, I still don't get it. g3dvl is currently in mesa because it is layered onto gallium. Your current VAAPI implementation is not layered onto gallium though? Or are you planning on implementing VAAPI on gallium? >> >>Well we already use a GLSL-like language for that (intermediate >>gallium representation) and we already have a working xvmc >>implementation, so I don't think these concerns hold. > > > Does the XVMC implementation support MC only flag or MC + IDCT? Both. > Is it efficient enough to decode high rate HD content? Yeah. > > Is it a high level language or you mean you do MC and IDCT with mesa internal > op? > I think a high level language is most useful for performance tuning and > debuging, consider the complexity of H.264 and post processing. Once we have proper shader optimization in the backends, that's actually going to save us some work. We can already decode video in real time without shader optimization, and it's only going to get better from there. Face it, we don't have enough developers here that we can afford to implement video decoding for each card specifically and then fine-tune the implementation. Which is why I'm going with a solution that works everywhere and that stacks up on the existing gallium 3D drivers. > > I have considered using GLSL, but for our media pipeline, > hardware usually run instruction in 16 ways or wider. Well it works fine for us... Stephane ------------------------------------------------------------------------------ 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
