From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 90510] [radeon][tahiti xt] IA_MULTI_VGT_PARAM programming seems broken
Date: Mon, 18 May 2015 13:26:24 +0000 [thread overview]
Message-ID: <bug-90510-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 888 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=90510
Bug ID: 90510
Summary: [radeon][tahiti xt] IA_MULTI_VGT_PARAM programming
seems broken
Product: Mesa
Version: git
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: critical
Priority: medium
Component: Drivers/Gallium/radeonsi
Assignee: dri-devel@lists.freedesktop.org
Reporter: sylvain.bertrand@gmail.com
QA Contact: dri-devel@lists.freedesktop.org
This is a follow-up of the bug #90370.
source engine games produce tons of graphical glitches, unless
R600_DEBUG='switch_on_eop' is defined.
Tested with dota2/portal2. For portal2, the amount of glitches depends on
the level you choose.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2329 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2015-05-18 13:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-18 13:26 bugzilla-daemon [this message]
2015-05-18 13:28 ` [Bug 90510] [radeon][tahiti xt] IA_MULTI_VGT_PARAM programming seems broken bugzilla-daemon
2015-05-18 17:09 ` bugzilla-daemon
2015-05-24 18:30 ` bugzilla-daemon
2015-05-25 14:42 ` bugzilla-daemon
2015-05-25 14:46 ` bugzilla-daemon
2015-06-12 16:37 ` bugzilla-daemon
2015-06-28 18:01 ` bugzilla-daemon
2015-06-28 18:05 ` 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-90510-502@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.