dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 80029] New: [bisected] HDMI Errors on drm-next & Linus's tree
Date: Sat, 14 Jun 2014 17:06:20 +0000	[thread overview]
Message-ID: <bug-80029-502@http.bugs.freedesktop.org/> (raw)


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

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

          Priority: medium
            Bug ID: 80029
          Assignee: dri-devel@lists.freedesktop.org
           Summary: [bisected] HDMI Errors on drm-next & Linus's tree
          Severity: normal
    Classification: Unclassified
                OS: All
          Reporter: mike@fireburn.co.uk
          Hardware: Other
            Status: NEW
           Version: XOrg CVS
         Component: DRM/Radeon
           Product: DRI

Created attachment 101055
  --> https://bugs.freedesktop.org/attachment.cgi?id=101055&action=edit
Dmesg

I'm getting mode not supported on my TV which is connected to a kabini system

It bisects back to:

d0c94692e0a360828745a469bcf90b5c4f9273d0 is the first bad commit
commit d0c94692e0a360828745a469bcf90b5c4f9273d0
Author: Mario Kleiner <mario.kleiner.de@gmail.com>
Date:   Thu Mar 27 19:59:39 2014 +0100

    drm/edid: Parse and handle HDMI deep color modes.

    Check the HDMI cea block for deep color mode bits. If available,
    assign the highest supported bpc for a hdmi display, corresponding
    to the given deep color modes.

    Signed-off-by: Mario Kleiner <mario.kleiner.de@gmail.com>
    Signed-off-by: Alex Deucher <alexander.deucher@amd.com>

:040000 040000 42cc03b8d280ed165276b9be1c337d52773c4c35
674f7984e5278ae8dc7080344304093020274839 M      drivers
:040000 040000 cfec2deeddc3827f444ed391efa9c06d8dedb846
50f255ca6a41a02eb039c9eb9a469f762c34df39 M      include


I'm attaching my dmesg of the errors I see - the EDID ones only appear once I
switch the TV / AV receiver off and on

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

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

             reply	other threads:[~2014-06-14 17:06 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-14 17:06 bugzilla-daemon [this message]
2014-06-14 17:07 ` [Bug 80029] [bisected] HDMI Errors on drm-next & Linus's tree bugzilla-daemon
2014-06-14 18:19 ` bugzilla-daemon
2014-06-14 18:50 ` bugzilla-daemon
2014-06-14 18:51 ` bugzilla-daemon
2014-06-15 15:30 ` bugzilla-daemon
2014-06-15 15:41 ` bugzilla-daemon
2014-06-15 16:23 ` bugzilla-daemon
2014-06-15 16:25 ` bugzilla-daemon
2014-06-15 16:45 ` bugzilla-daemon
2014-06-15 17:00 ` bugzilla-daemon
2014-06-15 17:01 ` bugzilla-daemon
2014-06-15 17:10 ` bugzilla-daemon
2014-06-15 18:41 ` bugzilla-daemon
2014-06-15 18:45 ` bugzilla-daemon
2014-06-15 18:50 ` bugzilla-daemon
2014-06-15 19:19 ` bugzilla-daemon
2014-06-15 19:32 ` bugzilla-daemon
2014-06-15 19:48 ` bugzilla-daemon
2014-06-16 14:10 ` bugzilla-daemon
2014-06-25 13:41 ` 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-80029-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;
as well as URLs for NNTP newsgroup(s).