Bug 79907 - Mesa 10.2.1 --enable-vdpau default=auto broken
Summary: Mesa 10.2.1 --enable-vdpau default=auto broken
Status: RESOLVED FIXED
Alias: None
Product: Mesa
Classification: Unclassified
Component: Mesa core (show other bugs)
Version: unspecified
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: mesa-dev
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-06-11 08:01 UTC by fredrik
Modified: 2014-06-12 17:09 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments

Description fredrik 2014-06-11 08:01:18 UTC
vdpau libs installed and mesa built with:

./configure --prefix=/usr --enable-gallium-egl --enable-gallium-gbm --enable-gallium-llvm --enable-gbm --enable-gles1 --enable-gles2 --enable-glx-tls --enable-osmesa --enable-texture-float --enable-xa --with-egl-platforms=drm --with-gallium-drivers=r300,r600,svga,swrast,radeonsi,nouveau

It appears mesa no longer automagically detects vdpau. Manually specifying --enable-vdpau builds the needed libs. It would be super if autodetection could be fixed again!
Comment 1 Emil Velikov 2014-06-11 21:48:45 UTC
Thanks for reporting, a silly thinko on my behalf is causing this behaviour.

Can you confirm that the patch [1] fixes the issue on your system ?

[1] http://patchwork.freedesktop.org/patch/27562/
Comment 2 Emil Velikov 2014-06-12 17:09:42 UTC
Managed to reproduce the problem and confirm that the patch fixes it.
Feel free to reopen if it's failing on your setup.

commit 816d392b586ecd95bd5b2dc24945bb9fc5d73d6e
Author: Emil Velikov <emil.l.velikov@gmail.com>
Date:   Wed Jun 11 22:15:58 2014 +0100

    configure: correctly autodetect xvmc/vdpau/omx

    Commit e62b7d38a1d (configure: autodetect video state-trackers
    when non swrast driver is present) added a check that caused
    the autodetection to be omitted when we have the swrast gallium
    driver. Whereas it should have skipped the VL targets when only
    swrast was selected.


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.