Re: [Mesa-dev] nouveau hardware decoding and vaDeriveImage

Hi Julien, thanks for providing some background on the issue. Now it makes a lot more sense. Am Mittwoch, den 16.08.2017, 10:40 +0100 schrieb Julien Isorce: > Hi, > > This issue is tracked here https://bugs.freedesktop.org/show_bug.cgi? > id=98285 > This is due to a limitation in libva API

Re: [Mesa-dev] nouveau hardware decoding and vaDeriveImage

Hi, This issue is tracked here https://bugs.freedesktop.org/s how_bug.cgi?id=98285 This is due to a limitation in libva API which only supports 1 FD per VaSurface. It is enough for intel-driver because NV12 is only 1 bo. But in nouveau driver, NV12 is 2 separates bo (omitting the interlaced pb).

Re: [Mesa-dev] nouveau hardware decoding and vaDeriveImage

[adding Julien, who did the nouveau va-api integration.] On Tue, Aug 15, 2017 at 9:59 AM, Philipp Kerling wrote: > Hi, > > I recently noticed that hardware video decoding with the nouveau driver > and libva does not play nicely with Wayland and decided to dig a bit. > > To

[Mesa-dev] nouveau hardware decoding and vaDeriveImage

Hi, I recently noticed that hardware video decoding with the nouveau driver and libva does not play nicely with Wayland and decided to dig a bit. To use libva in conjunction with Wayland in EGL applications, you usually export the surface dmabuf via vaDeriveImage & vaAcquireBufferHandle and then