Hi Jan,
I don't think we have implemented EGL interop on VA-API to this extend.
All that is supported is exporting the handle of RGBA images, not
directly decoded YUV data.
If you need decoding support with OpenGL/EGL interop on AMD hardware
please use VDPAU instead.
Regards,
Christian.
Am 15.07.2016 um 11:25 schrieb Jan Burgmeier:
Hi,
I am developing an application which uses vaapi and egl. My goal is to
use vaDeriveImage and vaAcquireBufferHandle to get the drm buffer id
which then can be used to create a EGLImageKHR. My problem is, that on
amd hardware (AMD GX-212ZC SOC with Radeon(TM) R1E Graphics and AMD
GX-424CC SOC with Radeon(TM) R5E Graphics) vaDeriveImage fails with
"invalid VASurfaceID" and when I do vaGetImage as a fallback to get
the image vaAcquireBufferHandle fails with "invalid VABufferID". The
same code works on Intel hardware.
Mesa version: 11.2.2
- Should this work in general?
- Is there any special setting needed?
Kind regards
Jan Burgmeier
___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/mesa-dev
___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/mesa-dev