https://bugs.freedesktop.org/show_bug.cgi?id=47846
--- Comment #6 from Ben Skeggs <[email protected]> 2012-04-13 01:03:37 PDT --- (In reply to comment #5) > After playing with xrandr and this new underscan parameter I have concluded > this is just an ugly workaround that doesn't fix the root problem which is > getting EDID right. > > Everything still looks wrong, I think the problem is that by using this > underscan thing the applications still think the resolution is 1366x768 when > its no longer the case. > And of course there is also the overscan at boot time problem. > > So is there any way to fix the way nouveau interprets the EDID data to make it > work like nvidia's driver? I'll add this to my list to look at. There is some hints in the EDID extension blocks that say whether or not a display will overscan a given resolution or not, and flags in the AVI InfoFrame that can (possibly) control it too. I looked into this at some point, and couldn't find a device that actually obeyed the specs so I didn't bother in the end. It's possible the NVIDIA binary driver is doing this I guess. However, for most displays, even with the NVIDIA binary driver you have to use their "Overscan Compensation" option too.. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. _______________________________________________ Nouveau mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/nouveau
