From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 85376] New: Dolphin emulator has bad colors
Date: Thu, 23 Oct 2014 17:48:05 +0000 [thread overview]
Message-ID: <bug-85376-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1311 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=85376
Bug ID: 85376
Summary: Dolphin emulator has bad colors
Product: Mesa
Version: unspecified
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/Gallium/r600
Assignee: dri-devel@lists.freedesktop.org
Reporter: ghallberg+bugzilla@gmail.com
Created attachment 108308
--> https://bugs.freedesktop.org/attachment.cgi?id=108308&action=edit
Fifo-file which displays the discoloration
When using recent versions of dolphin-emulator with open source amd drivers,
the graphics are tinted blue.
An example can be seen in this link: http://imgur.com/eLqLMdW
The example image was created when running the attached fifo-file in dolphin.
This is using the latest version of dolphin from the git-repo:
4.0.r3771.ce3a039-1 built with gcc 4.9.1-2 from the arch repositories
mesa is the 10.3.1 from the arch repositories and seems to be built with clang.
I'm running on an AMD A6-6400K APU.
I've tested the same versions of the software on my intel-based laptop, and the
discoloration is not present there.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2738 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:[~2014-10-23 17:48 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-23 17:48 bugzilla-daemon [this message]
2014-11-10 16:10 ` [Bug 85376] Dolphin emulator has bad colors bugzilla-daemon
2014-11-10 17:04 ` bugzilla-daemon
2014-11-10 17:08 ` bugzilla-daemon
2014-11-10 17:48 ` bugzilla-daemon
2014-11-10 19:25 ` bugzilla-daemon
2014-11-10 19:58 ` bugzilla-daemon
2014-11-10 20:01 ` bugzilla-daemon
2014-11-11 17:23 ` bugzilla-daemon
2014-11-11 19:05 ` bugzilla-daemon
2014-11-11 20:33 ` bugzilla-daemon
2014-11-11 21:31 ` bugzilla-daemon
2014-11-12 21:15 ` bugzilla-daemon
2014-11-14 18:06 ` bugzilla-daemon
2014-11-18 0:38 ` bugzilla-daemon
2014-11-20 2:49 ` bugzilla-daemon
2014-11-22 7:49 ` bugzilla-daemon
2014-11-22 7:51 ` bugzilla-daemon
2014-11-22 7:52 ` bugzilla-daemon
2014-11-22 15:11 ` bugzilla-daemon
2014-11-23 3: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-85376-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox