Hi,
one more heads up, just committed:
This module uses Xine's VDPAU output driver, but there's a patch required
sitting next to the module source. The patch has minimal impact and does not
affect the normal usage of the module at all.
With the patch applied and the special initialization data (visual) the
VDPAU
output driver provides us with the output surfaces rather than queueing them
at the presentation queue directly.
Each time a VdpOutputSurface is coming from the Xine output driver, we wrap
it into a DirectFB Surface by creating a preallocated surface in the VDPAU
pool.
This surface is then StretchBlit()ed to the desired destination
surface/rectangle
without any CPU intervention, as StretchBlit() just boils down to calling
OutputSurfaceRenderOutputSurface() in the graphics driver.
Tested successfully with sample1 and df_window.
TODO:
- avoid blitting when possible, pushing allocations into target surface,
e.g. layer
--
Best regards,
Denis Oliver Kropp
.------------------------------------------.
| DirectFB - Hardware accelerated graphics |
| http://www.directfb.org/ |
"------------------------------------------"
_______________________________________________
directfb-dev mailing list
directfb-dev@directfb.org
http://mail.directfb.org/cgi-bin/mailman/listinfo/directfb-dev
