From: Keith Packard <keithp@keithp.com>
To: Linus Torvalds <torvalds@linux-foundation.org>,
Robert Morell <rmorell@nvidia.com>
Cc: DRI mailing list <dri-devel@lists.freedesktop.org>
Subject: Re: "EDID checksum is invalid"
Date: Wed, 07 Jan 2015 23:05:22 -0800 [thread overview]
Message-ID: <86lhldeor1.fsf@hiro.keithp.com> (raw)
In-Reply-To: <CA+55aFyMR-k+cNxpyMSddfwAFWjS85rPP0eN86tD8sbUsOQ7WA@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 788 bytes --]
Linus Torvalds <torvalds@linux-foundation.org> writes:
> I'm assuming even the hdmi +5V line is under sw control at least for
> power management reasons. Maybe dpms off turns it off, and shouldn't?
> My monitor actually says "No HDMI (HML) Cable" when I do "xset dpms
> force off". Maybe that's normal, but maybe that's indicative of dpms
> turning things a bit *too* off?
How about getting a breakout cable so we can actually check the +5V
line to see when it turns off?
Total Phase makes one, although they only have the DVI ones in stock. A
couple of HDMI to DVI converters would let you use this.
http://www.totalphase.com/products/video-dvi/
I've even got an i2c protocol sniffer if you want to see what's going on
the DDC bus directly.
--
-keith
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 810 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:[~2015-01-08 7:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-07 2:01 "EDID checksum is invalid" Linus Torvalds
2015-01-07 6:07 ` Keith Packard
2015-01-07 6:21 ` Robert Morell
2015-01-07 6:42 ` Keith Packard
2015-01-07 17:07 ` Linus Torvalds
2015-01-07 17:51 ` Daniel Vetter
2015-01-07 18:03 ` Linus Torvalds
2015-01-08 7:05 ` Keith Packard [this message]
2015-01-07 7:32 ` Daniel Vetter
2015-01-07 17:51 ` Linus Torvalds
2015-01-07 20:06 ` Daniel Vetter
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=86lhldeor1.fsf@hiro.keithp.com \
--to=keithp@keithp.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=rmorell@nvidia.com \
--cc=torvalds@linux-foundation.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