[Bug 31943] drm EDID checking is too strict

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



https://bugs.freedesktop.org/show_bug.cgi?id=31943

--- Comment #12 from Alex Deucher <agd5f@xxxxxxxxx> 2011-04-08 09:05:29 PDT ---
(In reply to comment #11)
> I've got the problem as well.  I've got an older Hanns G JC199D, and apparently
> nouveau doesn't like its checksum either.

The edid parser is shared by all kms drm drivers.

> Is this a version problem, btw?  What is so offensive about these older EDID
> versions that the drivers are crapping out on (other than the checksum)?  Could
> the code validate the other sections to at least *see* if the data is garbage
> before throwing the whole block out?

Ideally, we implement some basic sanity checks to avoid reading past the end of
an edid with a bad checksum.  Usually the checksum problems are something
stupid like a vendor made a last minute change one of the fields or a
tv/receiver mangles something when updating hdmi fields.  IMHO, it would be
better to use the EDID than not.

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
_______________________________________________
dri-devel mailing list
dri-devel@xxxxxxxxxxxxxxxxxxxxx
http://lists.freedesktop.org/mailman/listinfo/dri-devel


[Index of Archives]     [Linux DRI Users]     [Linux Intel Graphics]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [XFree86]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Linux Kernel]     [Linux SCSI]     [XFree86]
  Powered by Linux