On Tue, May 17, 2016 at 3:16 PM, 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. > > Signed-off-by: Leo Liu <[email protected]>
Reviewed-by: Alex Deucher <[email protected]> > --- > src/gallium/state_trackers/va/context.c | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/src/gallium/state_trackers/va/context.c > b/src/gallium/state_trackers/va/context.c > index 93ab3d9..51abd87 100644 > --- a/src/gallium/state_trackers/va/context.c > +++ b/src/gallium/state_trackers/va/context.c > @@ -114,7 +114,6 @@ VA_DRIVER_INIT_FUNC(VADriverContextP ctx) > > switch (ctx->display_type) { > case VA_DISPLAY_ANDROID: > - case VA_DISPLAY_WAYLAND: > FREE(drv); > return VA_STATUS_ERROR_UNIMPLEMENTED; > case VA_DISPLAY_GLX: > @@ -127,6 +126,7 @@ VA_DRIVER_INIT_FUNC(VADriverContextP ctx) > if (!drv->vscreen) > goto error_screen; > break; > + case VA_DISPLAY_WAYLAND: > case VA_DISPLAY_DRM: > case VA_DISPLAY_DRM_RENDERNODES: { > drm_info = (struct drm_state *) ctx->drm_state; > -- > 2.7.4 > > _______________________________________________ > mesa-dev mailing list > [email protected] > https://lists.freedesktop.org/mailman/listinfo/mesa-dev _______________________________________________ mesa-dev mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/mesa-dev
