There are still bugs here with the current git version.
in hw/xfree86/modes/xf86Crtc.c:
handle_detailed_physical_size()
p->output->mm_width = det_mon->section.d_timings.h_size;
p->output->mm_height = det_mon->section.d_timings.v_size;
This unconditionally sets mm width and height from the detailed timings.
hw/xfree86/ddc/interpret_edid.c:
encode_aspect_ratio()
This function contains a quirk which determines whether the mm width and height
in the detailed timings presented by the monitor are actually the aspect ratio.
If so:
m->features.hsize = m->features.vsize = 0;
This results in a message like this in the log:
"Quirked EDID physical size to 0x0 cm"
Back to hw/xfree86/modes/xf86Crtc.c:
xf86OutputSetEDID()
In this function, if the mm width and height haven't been determined by
the DDC detailed timings probe (with no check whether they are valid),
they are then set to values in the max size field (features.hsize and
features.vsize) as long as it wasn't quirked to 0x0 due to the detailed
timings being invalid... ...too late now!
Of course, if no information is available, the xrandr output dimensions
needs to be set to something, whether that's 0x0 or 160x90 mm doesn't
matter so much, either way it's not reflecting reality. However, all
this convolution completely overrides the DisplaySize value the user may
have set. Since it's sourced in hw/xfree86/modes/xf86RandR12.c, but
then overridden during DDC mode probes it makes no difference.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/135738
Title:
DisplaySize setting not honored
To manage notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/135738/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
