Recent changes have been made to the VDPAU state tracker to make it unusable with nouveau. Don't provide users with an awfully slow "hardware" decoding option.
[To preemptively answer the question that will invariably be asked - this is due to the state tracker's use of PIPE_BIND_SHARED, which nouveau uses to force GART placement to make things with with PRIME. However when this is used for output surfaces, which are then blended on (the most common way of implementing an OSD), this results in *incredibly* slow operation.] Signed-off-by: Ilia Mirkin <imir...@alum.mit.edu> --- src/gallium/targets/vdpau/Makefile.am | 2 -- 1 file changed, 2 deletions(-) diff --git a/src/gallium/targets/vdpau/Makefile.am b/src/gallium/targets/vdpau/Makefile.am index d388f8b..9549a23 100644 --- a/src/gallium/targets/vdpau/Makefile.am +++ b/src/gallium/targets/vdpau/Makefile.am @@ -49,8 +49,6 @@ TARGET_DRIVERS = TARGET_CPPFLAGS = TARGET_LIB_DEPS = -include $(top_srcdir)/src/gallium/drivers/nouveau/Automake.inc - include $(top_srcdir)/src/gallium/drivers/r300/Automake.inc include $(top_srcdir)/src/gallium/drivers/r600/Automake.inc include $(top_srcdir)/src/gallium/drivers/radeonsi/Automake.inc -- 2.7.3 _______________________________________________ mesa-dev mailing list mesa-dev@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/mesa-dev
