From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 31943] [drm:radeon_dvi_detect] *ERROR* HDMI Type A-1: probed a monitor but no|invalid EDID
Date: Fri, 3 Dec 2010 20:06:47 -0800 (PST) [thread overview]
Message-ID: <20101204040648.1B16013004E@annarchy.freedesktop.org> (raw)
In-Reply-To: <bug-31943-502@http.bugs.freedesktop.org/>
https://bugs.freedesktop.org/show_bug.cgi?id=31943
Alban Browaeys <prahal@yahoo.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Attachment #40595|0 |1
is obsolete| |
--- Comment #5 from Alban Browaeys <prahal@yahoo.com> 2010-12-03 20:06:47 PST ---
Created an attachment (id=40792)
View: https://bugs.freedesktop.org/attachment.cgi?id=40792
Review: https://bugs.freedesktop.org/review?bug=31943&attachment=40792
Fix the version in the edid (v2.3 makes no sense) checksum is correct with v1.3
This patch is not good for upstream , ie if we had this fix why not add the
hundreds of other one for each broken edid kind.
Still it showcase the issue of this bug report.
First discarding the checksum would not help as here the reported incorrect
version is 2 and we only support 1 (thus the valid check would still fail).
The checksum is in fact correct if one replace this v2.3 by v1.3. It looks like
the version was mangled a posteriori.
One option is to completely discard the validity check via an option for the
drm module . Still it would move the issue to other layers if those expect a
valid edid or do a check of validity (they would also require a bypass option).
Another option is to load valid edid (from disk or initramfs,) like we do for
firmwares. One of the main issue of this approach is how to identify if and
which edid to load : phase out an id for the monitor or one for the invalid
edid (the latter via sum).
There are gaps to fill for this option though : will distro need to ship
hundreds of fixed edid in initramfs and such.
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next prev parent reply other threads:[~2010-12-04 4:06 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-31943-502@http.bugs.freedesktop.org/>
2010-11-29 15:08 ` [Bug 31943] [drm:radeon_dvi_detect] *ERROR* HDMI Type A-1: probed a monitor but no|invalid EDID bugzilla-daemon
2010-11-29 15:09 ` bugzilla-daemon
2010-12-04 4:06 ` bugzilla-daemon [this message]
2010-12-13 15:32 ` [Bug 31943] drm EDID checking is too strict bugzilla-daemon
2011-01-04 23:04 ` bugzilla-daemon
2011-01-08 17:33 ` bugzilla-daemon
2011-01-08 17:37 ` bugzilla-daemon
2011-01-10 19:16 ` bugzilla-daemon
2011-02-05 17:39 ` bugzilla-daemon
2011-04-08 15:25 ` bugzilla-daemon
2011-04-08 16:05 ` bugzilla-daemon
2011-05-05 16:14 ` bugzilla-daemon
2011-05-09 8:58 ` bugzilla-daemon
2011-05-09 8:59 ` bugzilla-daemon
2011-05-09 9:27 ` bugzilla-daemon
2011-05-09 9:29 ` bugzilla-daemon
2011-11-02 21:27 ` bugzilla-daemon
2019-10-14 13:20 ` 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=20101204040648.1B16013004E@annarchy.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).