From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 103968] No Hardware Acceleration with AMD RX 550
Date: Thu, 30 Nov 2017 10:55:58 +0000 [thread overview]
Message-ID: <bug-103968-502-brq7guiHRk@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-103968-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 3209 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=103968
--- Comment #2 from Odo Wolbers <moz-bugzilla.20.darkover@spamgourmet.com> ---
Here you are:
dpkg -l | grep '^i.*mesa'
ii glx-alternative-mesa 0.8.1
amd64 allows the selection of MESA as GLX provider
ii libegl-mesa0:amd64 17.2.5-1
amd64 free implementation of the EGL API -- Mesa vendor library
ii libegl1-mesa:amd64 17.2.5-1
amd64 transitional dummy package
ii libegl1-mesa-dev:amd64 17.2.5-1
amd64 free implementation of the EGL API -- development files
ii libegl1-mesa-drivers:amd64 13.0.6-1+b2
amd64 transitional dummy package
ii libgl1-mesa-dev:amd64 17.2.5-1
amd64 free implementation of the OpenGL API -- GLX development files
ii libgl1-mesa-dri:amd64 17.2.5-1
amd64 free implementation of the OpenGL API -- DRI modules
ii libgl1-mesa-glx:amd64 17.2.5-1
amd64 transitional dummy package
ii libglapi-mesa:amd64 17.2.5-1
amd64 free implementation of the GL API -- shared library
ii libgles2-mesa:amd64 17.2.5-1
amd64 transitional dummy package
ii libgles2-mesa-dev:amd64 17.2.5-1
amd64 free implementation of the OpenGL|ES 2.x API -- development files
ii libglu1-mesa:amd64 9.0.0-2.1
amd64 Mesa OpenGL utility library (GLU)
ii libglx-mesa0:amd64 17.2.5-1
amd64 free implementation of the OpenGL API -- GLX vendor library
ii libosmesa6:amd64 17.2.5-1
amd64 Mesa Off-screen rendering extension
ii libwayland-egl1-mesa:amd64 17.2.5-1
amd64 implementation of the Wayland EGL platform -- runtime
ii mesa-common-dev:amd64 17.2.5-1
amd64 Developer documentation for Mesa
ii mesa-opencl-icd:amd64 17.2.5-1
amd64 free implementation of the OpenCL API -- ICD runtime
ii mesa-utils 8.3.0-5
amd64 Miscellaneous Mesa GL utilities
ii mesa-utils-extra 8.3.0-5
amd64 Miscellaneous Mesa utilies (opengles, egl)
ii mesa-va-drivers:amd64 17.2.5-1
amd64 Mesa VA-API video acceleration drivers
ii mesa-vdpau-drivers:amd64 17.2.5-1
amd64 Mesa VDPAU video acceleration drivers
ii mesa-vulkan-drivers:amd64 17.2.5-1
amd64 Mesa Vulkan graphics drivers
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 3994 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2017-11-30 10:55 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-29 12:06 [Bug 103968] No Hardware Acceleration with AMD RX 550 bugzilla-daemon
2017-11-29 14:16 ` bugzilla-daemon
2017-11-29 14:24 ` bugzilla-daemon
2017-11-30 10:55 ` bugzilla-daemon [this message]
2017-11-30 11:10 ` bugzilla-daemon
2017-11-30 11:38 ` bugzilla-daemon
2017-11-30 11:44 ` bugzilla-daemon
2017-11-30 12:18 ` bugzilla-daemon
2017-11-30 14:59 ` bugzilla-daemon
2017-11-30 15:37 ` bugzilla-daemon
2017-11-30 15:43 ` bugzilla-daemon
2017-11-30 15:48 ` bugzilla-daemon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-103968-502-brq7guiHRk@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon@freedesktop.org \
--cc=dri-devel@lists.freedesktop.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox