On 17 May 2016 at 20:16, Leo Liu <[email protected]> wrote: > With xwayland, vainfo use VA_DISPLAY_WAYLAND as default and it fails > and fails when specify display with `vainfo --display wayland`. > In fact wayland support for libva uses drm path to connect device, > and should use drm pipe loader to create screen. > There are two codepaths which depends on actual wayland specifics that the summary fails to mention - vaGet{Surface,Image}BufferWl. Cool thing is that on my system none of the libva users has references to either of these two plus the latter isn't even implemented in the intel driver ;-)
For the future please document things a bit better ? As is the commit message is rather misleading. Thanks Emil _______________________________________________ mesa-dev mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/mesa-dev
