Well, as I understand here, the heart of the problem is:
"The problem is not caused by the driver, but by bad EDID data from the panel.
Bytes 66-67 (image size in mm) are simply copied over from bytes 21-22 (panel
size in cm) which is obviously incorrect." according to: https://bugs.freedesktop.org/show_bug.cgi?id=10304#c18
Should be fix upstream of X.org (I suppose EDID is some kind of module project for Xorg).
Rest of https://bugs.freedesktop.org/show_bug.cgi?id=10304, seems to be related to the fact that specifying display size in xorg.conf was not working.
So someone have given a patch in comment #14, but it was buggy, but with some patch to the patch, was finally fixed.
So the question is mostly, when and how it will be introduce in Hardy (if it is not already the case).
And to see if it fix it for everyone.
Well, as I understand here, the heart of the problem is: /bugs.freedeskt op.org/ show_bug. cgi?id= 10304#c18
"The problem is not caused by the driver, but by bad EDID data from the panel.
Bytes 66-67 (image size in mm) are simply copied over from bytes 21-22 (panel
size in cm) which is obviously incorrect." according to:
https:/
This can be better understood by reading EDID 1,1 data format at: en.wikipedia. org/wiki/ Extended_ display_ identification_ data
http://
Should be fix upstream of X.org (I suppose EDID is some kind of module project for Xorg).
Rest of https:/ /bugs.freedeskt op.org/ show_bug. cgi?id= 10304, seems to be related to the fact that specifying display size in xorg.conf was not working.
So someone have given a patch in comment #14, but it was buggy, but with some patch to the patch, was finally fixed.
So the question is mostly, when and how it will be introduce in Hardy (if it is not already the case).
And to see if it fix it for everyone.