All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 70934] [Regression] Problem with colors (depth?) on DCE5 Barts (HD69xx)
Date: Sun, 27 Oct 2013 23:16:23 +0000	[thread overview]
Message-ID: <bug-70934-502-TboTdMIxym@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-70934-502@http.bugs.freedesktop.org/>


[-- Attachment #1.1: Type: text/plain, Size: 916 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=70934

--- Comment #4 from Rafał Miłecki <zajec5@gmail.com> ---
I was bisecting over commits touching drivers/gpu/ only, but the one I found
seems pretty likely:

eccea7920cfb009c2fa40e9ecdce8c36f61cab66 is the first bad commit
commit eccea7920cfb009c2fa40e9ecdce8c36f61cab66
Author: Alex Deucher <alexander.deucher@amd.com>
Date:   Mon Mar 26 15:12:54 2012 -0400

    drm/radeon/kms: improve bpc handling (v2)

    Improve handling of bpc (bits per color) in radeon.
    In most cases we want 8 except for HDMI, DP, LVDS, and eDP.

    v2: handle DP better.

    Signed-off-by: Alex Deucher <alexander.deucher@amd.com>
    Tested-by: Lennert Buytenhek <buytenh@wantstofly.org>
    Signed-off-by: Dave Airlie <airlied@redhat.com>

I'll verify that further tomorrow.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 1973 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

  parent reply	other threads:[~2013-10-27 23:16 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-27 21:01 [Bug 70934] New: [Regression] Problem with colors (depth?) on DCE5 Barts (HD69xx) bugzilla-daemon
2013-10-27 21:12 ` [Bug 70934] " bugzilla-daemon
2013-10-27 21:17 ` bugzilla-daemon
2013-10-27 21:20 ` bugzilla-daemon
2013-10-27 23:16 ` bugzilla-daemon [this message]
2013-10-27 23:17 ` bugzilla-daemon
2013-10-28  7:35 ` bugzilla-daemon
2013-10-28  7:35 ` bugzilla-daemon
2013-10-28  7:51 ` bugzilla-daemon
2013-10-28  8:56 ` bugzilla-daemon
2013-10-28  9:08 ` bugzilla-daemon
2013-10-28  9:08 ` bugzilla-daemon
2013-10-28 13:55 ` bugzilla-daemon
2013-10-28 15:07 ` bugzilla-daemon
2013-10-28 15:37 ` bugzilla-daemon
2013-10-28 17:56 ` bugzilla-daemon
2013-10-28 22:10 ` bugzilla-daemon
2013-10-29  6:21 ` bugzilla-daemon
2013-10-29  6:22 ` bugzilla-daemon
2013-10-29 15:05 ` bugzilla-daemon
2014-01-06 21:34 ` 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-70934-502-TboTdMIxym@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.