diff options
| author | Leo Liu <leo.liu@amd.com> | 2016-05-17 15:16:09 -0400 |
|---|---|---|
| committer | Leo Liu <leo.liu@amd.com> | 2016-05-19 09:40:33 -0400 |
| commit | 2f90d11d86e476c679abbc0420ea22bd14b53ef7 (patch) | |
| tree | eb3d0883a00c2e63f7f20bcd7567d94f31876489 | |
| parent | f6742859b76de8c90a8593f2f308e7c22380a390 (diff) | |
st/va: use drm render node for wayland display type
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 <leo.liu@amd.com>
Reviewed-by: Alex Deucher <alexander.deucher@amd.com>
| -rw-r--r-- | src/gallium/state_trackers/va/context.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/src/gallium/state_trackers/va/context.c b/src/gallium/state_trackers/va/context.c index 93ab3d98ec2..51abd87cc4e 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; |