From: Robert Morell <rmorell@nvidia.com>
To: Keith Packard <keithp@keithp.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
DRI mailing list <dri-devel@lists.freedesktop.org>
Subject: Re: "EDID checksum is invalid"
Date: Tue, 6 Jan 2015 22:21:09 -0800 [thread overview]
Message-ID: <20150107062109.GA32123@morell.nvidia.com> (raw)
In-Reply-To: <86387nrum9.fsf@hiro.keithp.com>
On Tue, Jan 06, 2015 at 10:07:58PM -0800, Keith Packard wrote:
> * PGP Signed by an unknown key
>
> Linus Torvalds <torvalds@linux-foundation.org> writes:
>
> > it looks like the beginning is the same, but then it just turns to all
> > ones at a random point (even *within* a byte).
>
> Looks like the EDID ROM is dropping off the i2c bus in the middle of the
> transfer. Wonder if it's being 'clever' if things go too slowly at some
> point, or if there's a bug in the DDC code that's in use.
FWIW, I've seen that exact symptom on some monitors when the +5V pin on
the DVI or HDMI cable from the GPU isn't enabled (or isn't providing
enough current). Some monitors power the i2c/edid/DDC logic from that
+5V either exclusively or when in the DPMS off state, and the i2c chip
will just stop responding after a few cycles if not provided sufficient
power.
- Robert
_______________________________________________
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-07 6:21 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 [this message]
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
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=20150107062109.GA32123@morell.nvidia.com \
--to=rmorell@nvidia.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=keithp@keithp.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