Ticket #2269 (closed enhancement: fixed)
(E-)EDID writing (DDC/CI)
|Reported by:||ticket||Owned by:||somebody|
Numerous people are currently suffering from display problems due to incorrectly shipped or (e.g. through a KVM switch) inaccessible EDID information - sometimes in the base 128 bytes, sometimes in the additional record of a 256-byte E-EDID.
Most of the EEPROMs badly programmed by TFT manufacturers are not write-protected, so the bugs could be (and are being, cf. http://www.hardforum.com/showthread.php?t=1232024) fixed by enterprising users in many cases.
Therefore, I would appreciate to learn whether the discussion regarding the creation of a set-edid or write-edid tool at http://osdir.com/ml/drivers.sensors/2005-06/msg00080.html has come to anything.
Sure enough, as indicated in the above thread, misusing such tools could at least temporarily wreck some devices, but then again so can many things, in particular needlessly shipping hardware to the vendor (who may not even have an update) for "repairs" although it could perfectly well be reprogrammed over the DVI connection (after the appropriate, explicit warning).
Non-exhaustive list of other code that has been found to this end: