On Tue, Jan 20, 2009 at 4:07 AM, Xavier Bestel <xavier.bes...@free.fr> wrote: > Sorry to get in the way, but if at some point in the pipe everything can > be done in hardware or shaders, maybe drivers should expose what they > can accelerate to let the app handle the rest (some smart frameworks > like gstreamer could take shortcuts). > OTOH that could require a more complex interface.
That was the original plan. It really depends on the API the client is actually using (VAAPI, VDPAU, etc). The VAAPI interface is flexible enough to let drivers expose the entrypoints they support, so the app does everything up to that point and hands off the rest to the driver. Unfortunately VDPAU doesn't do that, the app passes the bitstream off to the driver and the driver gets to do everything else, which is why we need a more complete implementation on the driver side. Even if VAAPI had made it out to mplayer and others I don't know that they would have bothered to support all the possible entry points anyway, since its a lot of work for them to hack up their current decoders. ------------------------------------------------------------------------------ This SF.net email is sponsored by: SourcForge Community SourceForge wants to tell your story. http://p.sf.net/sfu/sf-spreadtheword _______________________________________________ Mesa3d-dev mailing list Mesa3d-dev@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mesa3d-dev
