From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 80029] [bisected] HDMI Errors on drm-next & Linus's tree
Date: Sun, 15 Jun 2014 15:30:59 +0000 [thread overview]
Message-ID: <bug-80029-502-s4cIx9izpX@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-80029-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 1297 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=80029
--- Comment #5 from Mario Kleiner <mario.kleiner@tuebingen.mpg.de> ---
(In reply to comment #3)
> Hi Mario
>
> I'm not sure about other video modes - I always use the native 1080p @ 60Hz
> I'm not sure how to change it either when I can't see the screen
>
> I've attached the verbose xrandr output for you from a working kernel
>
Thanks. The edid looks ok and spec conformant. If the edid doesn't lie about
your device, we should be able to drive your tv with a 12 bit deep color mode
at full resolution without problems.
> Would you like the debugging put on a working or broken kernel?
On the 3.16 kernel.
>
> I don't remember ever seeing any EDID issues except when the receiver was on
> but the TV was off
Hm. Can you explain your setup? The TV isn't connected directly to the graphics
card, but there's some 3rd party receiver inbetween? Can you give me the
name/model of the receiver and TV?
The hdmi deep color code has been successfully tested on different panels with
dce-4 and dce-6 graphics cards, but not with the latest dce-8 kabini's. This
could be something missing in the driver specific to dce-8, or your tv
misrepresenting its capabilities.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2250 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:[~2014-06-15 15:30 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-14 17:06 [Bug 80029] New: [bisected] HDMI Errors on drm-next & Linus's tree bugzilla-daemon
2014-06-14 17:07 ` [Bug 80029] " 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 [this message]
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-s4cIx9izpX@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).