Context Navigation

Changes between Version 1 and Version 2 of Ticket #17432, comment 11

v1	v2
3	3	On that driver I have a trick to fetch the 'native' modeline from registers in the card as programmed by the BIOS (at least, its the highest mode that can be done over there) is case fetch EDID fails.
4	4
5		In case it fails over there I also check for the ~~low~~est common mode from the connected screens and return that for compatibility (Because app_Server doesn't support two seperate screens yet). On top of that I do compatibility checks on aspect. The modelist returned to app_Server there are filtered (other hook) so only widescreen modes would be offered to use if the screen is widescreen, and vice versa if it's all 4:3 (5:4) aspect.
	5	In case it fails over there I also check for the highest common mode from the connected screens and return that for compatibility (Because app_Server doesn't support two seperate screens yet). On top of that I do compatibility checks on aspect. The modelist returned to app_Server there are filtered (other hook) so only widescreen modes would be offered to use if the screen is widescreen, and vice versa if it's all 4:3 (5:4) aspect.
6	6
7	7	That's overkill maybe and I don't know if these days it still has the same effect in screenprefs, because, as you just showed, app_server itself checks EDID and might come' in the way' of what the driver actually wanted to make happen.