From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 89699] Regression in 10.5.1 causes flickering/artifacting in a particular video game
Date: Tue, 09 Jun 2015 07:10:51 +0000 [thread overview]
Message-ID: <bug-89699-502-M2iHhJkiAg@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-89699-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 1028 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=89699
--- Comment #12 from Marek Olšák <maraeo@gmail.com> ---
(In reply to Sergio Pais from comment #11)
> Hello,
>
> The following is the result of bisecting:
>
> 0543630d0b0d9d9f6eefbc14fbd3385d4de37ba0 is the first bad commit
> commit 0543630d0b0d9d9f6eefbc14fbd3385d4de37ba0
> Author: Marek Olšák <marek.olsak@amd.com>
> Date: Sun Jan 4 22:01:43 2015 +0100
>
> radeonsi: only set BC_OPTIMIZE_DISABLE when necessary
>
> SPI_PS_IN_CONTROL is moved into the SPI mapping state.
>
> Reviewed-by: Michel Dänzer <michel.daenzer@amd.com>
>
> :040000 040000 1cf87184549eeb5432cc02fbb352c10f873ffd9f
> 8d8f7873bdcaf67167ec744265d008306e53d901 M src
>
>
> http://cgit.freedesktop.org/mesa/mesa/commit/
> ?id=0543630d0b0d9d9f6eefbc14fbd3385d4de37ba0
Sorry to bring you bad news, but that commit was reverted soon after it was
committed.
Marek
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2172 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 prev parent reply other threads:[~2015-06-09 0:10 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-89699-502@http.bugs.freedesktop.org/>
2015-03-21 10:43 ` [Bug 89699] Regression in 10.5.1 causes flickering/artifacting in a particular video game bugzilla-daemon
2015-03-21 16:32 ` bugzilla-daemon
2015-03-23 1:43 ` bugzilla-daemon
2015-03-23 22:56 ` bugzilla-daemon
2015-03-24 14:49 ` bugzilla-daemon
2015-04-07 20:22 ` bugzilla-daemon
2015-04-07 20:40 ` bugzilla-daemon
2015-04-10 22:26 ` bugzilla-daemon
2015-06-09 5:53 ` bugzilla-daemon
2015-06-09 7:10 ` bugzilla-daemon [this message]
2015-06-09 7:57 ` bugzilla-daemon
2015-06-09 9:06 ` bugzilla-daemon
2015-06-29 4:49 ` bugzilla-daemon
2015-07-12 12:47 ` bugzilla-daemon
2015-07-12 12:48 ` bugzilla-daemon
2015-07-12 12:49 ` bugzilla-daemon
2015-07-13 10:18 ` bugzilla-daemon
2015-07-14 1:14 ` bugzilla-daemon
2015-07-15 8:04 ` bugzilla-daemon
2015-07-17 21:22 ` bugzilla-daemon
2015-07-18 8:58 ` bugzilla-daemon
2015-07-18 11:49 ` bugzilla-daemon
2015-07-18 11:52 ` bugzilla-daemon
2015-07-18 12:46 ` bugzilla-daemon
2015-07-18 12:54 ` bugzilla-daemon
2015-08-05 3:31 ` bugzilla-daemon
2015-08-05 3:55 ` 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-89699-502-M2iHhJkiAg@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