From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 91136] [tahiti xt] portal2 glitchy without R600_DEBUG=switch_on_eop
Date: Sun, 28 Jun 2015 18:10:37 +0000 [thread overview]
Message-ID: <bug-91136-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 892 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=91136
Bug ID: 91136
Summary: [tahiti xt] portal2 glitchy without
R600_DEBUG=switch_on_eop
Product: Mesa
Version: unspecified
Hardware: Other
OS: All
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/Gallium/radeonsi
Assignee: dri-devel@lists.freedesktop.org
Reporter: sylvain.bertrand@gmail.com
QA Contact: dri-devel@lists.freedesktop.org
play "the reunion"/"propulsion flings"
Without R600_DEBUG=switch_on_eop, glitches are unbearable.
With R600_DEBUG=switch_on_eop, nearly 0 glitch.
latest linux from agd5f linux 4.1 fixes. drm/llvm/mesa/xserver/xf86-video-ati
straight from git (yesterday)
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2204 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-06-28 18:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-28 18:10 bugzilla-daemon [this message]
2015-06-28 18:13 ` [Bug 91136] [tahiti xt] portal2 glitchy without R600_DEBUG=switch_on_eop bugzilla-daemon
2015-06-28 18:17 ` [Bug 91136] [tahiti xt] portal2/dota2 " bugzilla-daemon
2015-07-16 21:24 ` bugzilla-daemon
2015-07-29 1:28 ` bugzilla-daemon
2015-07-29 21:50 ` bugzilla-daemon
2015-08-02 22:31 ` bugzilla-daemon
2015-08-03 23:52 ` bugzilla-daemon
2016-07-21 11:45 ` 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-91136-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.