Hey,
Could you say what's status of fixing that problem? I see Alex patch is
not included to the Kernel for the some reason.
Could you point out what is recommended workaround for that bug as now?
I have that known bad behaving Acer AL2216W monitor...
regards
Antti
--
http://palosaari.fi/
__
Hey,
Could you say what's status of fixing that problem? I see Alex patch is
not included to the Kernel for the some reason.
Could you point out what is recommended workaround for that bug as now?
I have that known bad behaving Acer AL2216W monitor...
regards
Antti
--
http://palosaari.fi/
On Tue, 2011-01-04 at 18:00 -0500, Alex Deucher wrote:
> Lots of EDIDs have bad checksums or bad version numbers, but
> have otherwise good data in them. The current code rejects
> them which results in bad modes or blank screens in some cases.
> This patch adds a new module parameter, edid_strict
On Tue, 2011-01-04 at 18:00 -0500, Alex Deucher wrote:
> Lots of EDIDs have bad checksums or bad version numbers, but
> have otherwise good data in them. The current code rejects
> them which results in bad modes or blank screens in some cases.
> This patch adds a new module parameter, edid_strict
Lots of EDIDs have bad checksums or bad version numbers, but
have otherwise good data in them. The current code rejects
them which results in bad modes or blank screens in some cases.
This patch adds a new module parameter, edid_strict, to drm.ko.
It defaults to 1 (strict conformance, the current
Lots of EDIDs have bad checksums or bad version numbers, but
have otherwise good data in them. The current code rejects
them which results in bad modes or blank screens in some cases.
This patch adds a new module parameter, edid_strict, to drm.ko.
It defaults to 1 (strict conformance, the current
