From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 110783] Mesa 19.1 rc crashing MPV with VAAPI
Date: Wed, 12 Jun 2019 17:31:24 +0000 [thread overview]
Message-ID: <bug-110783-502-JaUkoGPNwM@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-110783-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 747 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=110783
--- Comment #8 from Ilia Mirkin <imirkin@alum.mit.edu> ---
(In reply to Gert Wollny from comment #7)
> This is a very deep rabbit hole: Not only does r600 not support DIV, it also
> doesn't support TEX_LZ that is used by these compute shaders and Evergreen
> class hardware doesn't support more then one target swizzle for the
> destinations with RCP so that the shader is even more broken. I think the
> best option now will be to disable this shader for now for this hardware.
The state tracker has to respect PIPE_CAP's. If the driver doesn't say it has
DIV or TEX_LZ, then those shouldn't be used.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1587 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2019-06-12 17:31 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-28 13:11 [Bug 110783] Mesa 19.1 rc crashing MPV with VAAPI bugzilla-daemon
2019-05-28 13:11 ` bugzilla-daemon
2019-06-10 21:47 ` bugzilla-daemon
2019-06-11 7:06 ` bugzilla-daemon
2019-06-12 14:24 ` bugzilla-daemon
2019-06-12 15:01 ` bugzilla-daemon
2019-06-12 15:16 ` bugzilla-daemon
2019-06-12 17:25 ` bugzilla-daemon
2019-06-12 17:31 ` bugzilla-daemon [this message]
2019-06-12 18:42 ` bugzilla-daemon
2019-06-12 19:31 ` bugzilla-daemon
2019-06-13 2:22 ` bugzilla-daemon
2019-06-13 7:35 ` bugzilla-daemon
2019-06-13 15:46 ` bugzilla-daemon
2019-06-13 16:25 ` bugzilla-daemon
2019-06-14 14:28 ` bugzilla-daemon
2019-06-14 15:15 ` bugzilla-daemon
2019-06-17 14:11 ` bugzilla-daemon
2019-06-26 17:58 ` bugzilla-daemon
2019-06-28 13:39 ` bugzilla-daemon
2019-07-08 16:10 ` bugzilla-daemon
2019-07-09 9:38 ` bugzilla-daemon
2019-07-09 13:14 ` bugzilla-daemon
2019-07-11 12:58 ` bugzilla-daemon
2019-07-11 17:52 ` bugzilla-daemon
2019-07-11 21:25 ` bugzilla-daemon
2019-07-13 6:17 ` 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-110783-502-JaUkoGPNwM@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.