From: Adam Jackson <ajax@redhat.com>
To: Alexander Beregalov <a.beregalov@gmail.com>
Cc: dri-devel@lists.freedesktop.org
Subject: Re: [radeon] EDID checksum is invalid
Date: Tue, 06 Dec 2011 12:52:41 -0500 [thread overview]
Message-ID: <4EDE5669.5070002@redhat.com> (raw)
In-Reply-To: <CAA1sL1TzS3bqWJeWu7+HrFJtz+BB1YwU6uwFfxPJyem+qgT3Bg@mail.gmail.com>
On 12/5/11 3:39 PM, Alexander Beregalov wrote:
> At boot time:
> [drm:drm_edid_block_valid] *ERROR* EDID checksum is invalid, remainder is 206
> Raw EDID:
> 27 0f 01 03 80 26 1e 78 2a de 95 a3 54 4c 99 26
> 0f 50 54 bf ef 80 81 80 81 40 71 4f 01 01 01 01
> 01 01 01 01 01 01 30 2a 00 98 51 00 2a 40 30 70
> 13 00 78 2d 11 00 00 1e 00 00 00 fd 00 38 4b 1e
> 51 0e 00 0a 20 20 20 20 20 20 00 00 00 fc 00 53
> 79 6e 63 4d 61 73 74 65 72 0a 20 20 00 00 00 ff
> 00 48 53 47 59 39 30 37 30 33 32 0a 20 20 00 59
> ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
This looks like an EDID fetch of bytes 16 through 143, instead of 0
through 127 (ie, skip the first 16, last 16 filled with -1).
> Few days after that:
> [drm:drm_edid_block_valid] *ERROR* EDID checksum is invalid, remainder is 38
> Raw EDID:
> 30 2a 00 98 51 00 2a 40 30 70 13 00 78 2d 11 00
> 00 1e 00 00 00 fd 00 38 4b 1e 51 0e 00 0a 20 20
> 20 20 20 20 00 00 00 fc 00 53 79 6e 63 4d 61 73
> 74 65 72 0a 20 20 00 00 00 ff 00 48 53 47 59 39
> 30 37 30 33 32 0a 20 20 00 59 ff ff ff ff ff ff
> ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
Offset of 54 bytes here, which is weirder.
Possibly the i2c code isn't resetting the index to 0 when it needs to.
- ajax
prev parent reply other threads:[~2011-12-06 19:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-05 20:39 [radeon] EDID checksum is invalid Alexander Beregalov
2011-12-06 13:50 ` Alex Deucher
2011-12-06 17:52 ` Adam Jackson [this message]
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=4EDE5669.5070002@redhat.com \
--to=ajax@redhat.com \
--cc=a.beregalov@gmail.com \
--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 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.