Bastien,
Broken monitors and/or broken graphic boards may send erroneous or no
EDID data. This also applies to broken KVM devices that are unable to
correctly forward the EDID data of the connected monitor but invent
their own fantasy data.
This patch allows to specify an EDID data set to be used instead of
probing the monitor for it. It contains built-in data sets of frequently
used screen resolutions. In addition, a particular EDID data set may be
provided in the /lib/firmware directory and loaded via the firmware
interface. The name is passed to the kernel as module parameter of the
drm_kms_helper module either when loaded
options drm_kms_helper edid_firmware=edid/1280x1024.bin
or as kernel commandline parameter
drm_kms_helper.edid_firmware=edid/1280x1024.bin
Windows allow vendor to override eddid based on 3 bytes manufacturer
and product code.
This may solve the situation when a particular monitor lies about the
required setting or its EDID data set has an invalid CRC. However, this
does not solve the situation when we do not get any useful EDID
information, because something is totally broken. This also applies to
the KVM situation when the KVM sends EDID data that are totally
unrelated to the monitor at the other side of the KVM.
Seems a reasonnable approach to follow.
I am not yet convinced.
-Carsten.
_______________________________________________
dri-devel mailing list
dri-devel@xxxxxxxxxxxxxxxxxxxxx
http://lists.freedesktop.org/mailman/listinfo/dri-devel
