From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 99078] Desktop icons oversaturated with red after December 11 2016 update
Date: Mon, 23 Jan 2017 14:44:39 +0000 [thread overview]
Message-ID: <bug-99078-502-a1l3kwCa8f@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-99078-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 913 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=99078
--- Comment #29 from Nicolai Hähnle <nhaehnle@gmail.com> ---
It's almost certainly because we missed
01a133c760ebb8db1e204f76ba55c19558b1ce01 "AMDGPU: Do not clobber SCC in
SIWholeQuadMode" when back-porting -- probably because that one is not
straight-forward at all to back-port. The best course of action would indeed be
to revert that commit; IIRC it fixes a bug in Kodi, but the impact of that is
much less than widespread weird tints.
The part that really sucks is that I don't think an LLVM 3.9.2 is planned. We
need to keep an eye out on whether this causes a problem in any distribution
default installation.
FWIW, I haven't seen a problem in Ubuntu 16.10 even though it does have LLVM
3.9.1, probably because the default installation of Mesa is ancient.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1741 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-01-23 14:44 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-99078-502@http.bugs.freedesktop.org/>
2016-12-15 7:13 ` [Bug 99078] Desktop icons oversaturated with red after December 11 2016 update bugzilla-daemon
2016-12-15 10:01 ` bugzilla-daemon
2016-12-20 23:15 ` bugzilla-daemon
2016-12-21 2:51 ` bugzilla-daemon
2016-12-21 6:58 ` bugzilla-daemon
2016-12-21 7:00 ` bugzilla-daemon
2016-12-21 11:01 ` bugzilla-daemon
2016-12-21 22:23 ` bugzilla-daemon
2016-12-24 0:25 ` bugzilla-daemon
2016-12-28 21:25 ` bugzilla-daemon
2016-12-31 10:58 ` bugzilla-daemon
2017-01-09 23:11 ` bugzilla-daemon
2017-01-20 17:40 ` bugzilla-daemon
2017-01-20 20:28 ` bugzilla-daemon
2017-01-20 20:31 ` bugzilla-daemon
2017-01-21 0:28 ` bugzilla-daemon
2017-01-21 0:29 ` bugzilla-daemon
2017-01-21 4:29 ` bugzilla-daemon
2017-01-21 7:25 ` bugzilla-daemon
2017-01-23 14:24 ` bugzilla-daemon
2017-01-23 14:27 ` bugzilla-daemon
2017-01-23 14:44 ` bugzilla-daemon [this message]
2017-01-23 14:45 ` bugzilla-daemon
2017-01-23 15:03 ` bugzilla-daemon
2017-01-23 16:58 ` bugzilla-daemon
2017-01-24 1:15 ` bugzilla-daemon
2017-02-07 8:27 ` bugzilla-daemon
2017-02-07 9:00 ` bugzilla-daemon
2018-04-11 6:00 ` 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-99078-502-a1l3kwCa8f@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