The advantage of binding between Surface and Context.
by Hirokazu Honda
Hi,
According to libva document
(http://01org.github.io/libva_staging_doxygen/group__api__core.html#ga4af3...),
Surfaces are bound to a context if passing them as an argument when
creating the context.
Seeing intel-vaapi-driver code, the surfaces are just stored in
object_context.render_targets.
A surface processed by
vaBeginPicture()-vaRenderPicture()-vaEndPicture() are specified in
vaBeginPicture(). (object_context.current_render_target)
It looks like a surface can be processed using a context by being
specified in vaBeginPicture(), even if it is not bound to the context.
Here, my questions are below.
What is the advantage of binding?
In what circumstances do we need to associate the context with surfaces?
In which scenarios passing surfaces to vaCreateContext is required,
and in which it is not?
Best Regards,
Hirokazu Honda
3 years
Need support for intel-vaapi driver on vxworks
by Gurpartap Singh
We are porting intel-vaapi driver and libva to vxworks 7. Vxworks7
provides libdrm2.4.74 and i915 and DRM driver for intel E3825 SOC. We try
to achieve H264 encoding. But encoded video we are getting is corrupted. Is
there any pointer we can debug ?
3 years, 5 months
