vaGetSurfaceBufferWl() is not implemented at VAAPI Gallium state tracker, which prevents it's usage under Wayland. But, after the DRI3 patches for hardware video decoding landed, NOT_IMPLEMENTED return was removed, making the false sense what this will work under Wayland as expected[1]. But it's still don't. See the bug referenced under "See Also". Also, I don't know actually, under which component should I file this bug. So redirect me if I had mistaken. [1]: https://cgit.freedesktop.org/mesa/mesa/tree/src/gallium/state_trackers/va/context.c#n129
First, the change is nothing to do with DRI3. Second, the change removing "NOT_IMPLEMENTED" is wayland display should be opened with DRM code path, and it's already implemented. the code here is not general switch to turn on the wayland support on vaapi, it's just one of the steps to complete that support and which has been implemented. Sorry for the confusion.
Egor, does reverting commit 2f90d11d ("st/va: use drm render node for wayland display type") make totem work on Wayland?
(In reply to Michel Dänzer from comment #2) > Egor, does reverting commit 2f90d11d ("st/va: use drm render node for > wayland display type") make totem work on Wayland? No. This makes it just crash with Segfault.
I found an issue with Totem player with DRI3 enabled, which is about glx of gstreamer-vaapi, it renews temporary pixmap each frame. I got a fix and have it sent to mesa-dev lists. But this is glx related, not sure if it will helps your case.
This affect gstreamer playback in wayland (weston). gst-play-1.0 --videosink vaapisink some_file.mp4 fails because vaGetSurfaceBufferWl is not implemented.
-- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/mesa/mesa/issues/587.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.