From: Keith Packard <keithp@keithp.com>
To: Robert Morell <rmorell@nvidia.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
DRI mailing list <dri-devel@lists.freedesktop.org>
Subject: Re: "EDID checksum is invalid"
Date: Tue, 06 Jan 2015 22:42:57 -0800 [thread overview]
Message-ID: <86zj9vqefi.fsf@hiro.keithp.com> (raw)
In-Reply-To: <20150107062109.GA32123@morell.nvidia.com>
[-- Attachment #1.1: Type: text/plain, Size: 618 bytes --]
Robert Morell <rmorell@nvidia.com> writes:
> 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.
Makes sense -- the chip will power itself from the i2c when not
transmitting, and can talk until whatever energy is stored in various
capacitors on the Vcc rail discharge.
--
-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-07 6:43 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 [this message]
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=86zj9vqefi.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 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.