retitle 253607 xserver-xfree86: [debconf] don't set monitor sync ranges in config file at all; just rely on DDC/EDID to work severity 253607 wishlist thanks > Like said, since XFree 4.3.0, Xfree, at least on the graphic drivers > that support it, is capable to run without monitor timings, and able to > ask the monitor this over the ddc protocol. ...except you don't always get an answer back. > Ideally, the configuration stuff should somehow interogate the graphic > card/monitor, and see if it is able to use the ddc protocol to get the > datas, tell the user that this values were detected, and ask if he want > to use the default values, autodetect each time, or provide some values > himself, the default being autodetecting stuff. Yes, "somehow". You don't provide any code, or anything beyond the barest sketch of a design really, so this is going to have to wait until after sarge. > By letting these entries absent of the config file, at worst X will > revert to some VGA standard mode, so there is no danger, but you may get > reports about "why are the icons so big" from people without monitor > attached, or using broken monitor switches or such. VGA standard mode is far too crude for most purposes today. Modern desktops expect to have a ton of real estate, which is why I have added 1152x768 and 1024x768 to the fallback default mode list in the current "debconf overhaul" work being done in XSF SVN. > I guess read-edid can be used for just this, but then maybe it is x86 > only, is that possible ? Actually, Colin Watson has done some work to make read-edid operate on PowerPC as well[1]. I hope to get that patch applied in time for sarge; I have authorized an NMU for someone else to do so if people don't think I will get to it in time. On a more general note, now that the licensing of the X-Oz autoconfig stuff has been clarified (it did exist under traditional MIT/X11 terms when it was first checked into XFree86 CVS), it may be that in sarge + 1 when we migrate to X.Org we will use "X -autoconfig" instead of (or as an alternative to) the combination of discover, mdetect, and read-edid. My only concern about that approach is we'd better be damn sure starting X doesn't lock up people's machines, especially on our more exotic architectures. discover and mdetect don't, and read-edid only seems to hurt x86 users with buggy hardware. [1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=262102 -- G. Branden Robinson | If you wish to strive for peace of Debian GNU/Linux | soul, then believe; if you wish to branden@debian.org | be a devotee of truth, then http://people.debian.org/~branden/ | inquire. -- Friedrich Nietzsche
Attachment:
signature.asc
Description: Digital signature