Chris Lumens <clumens@xxxxxxxxxx> wrote: > Rahul Sundaram wrote: > > I think the answer is that Xorg is moving into the direction of getting > > things working properly by default by instead of having the user fiddle > > with settings. The Xorg auto configuration mechanism in FC6 works better > > and usually gets things right. If there are problems file bug reports > > and help fix the issue rather than workaround it with configuration > > tools and files manually. For Xorg 7.3, the plan is to use HAL and DBus > > to enhance this further. Also see http://fedoraproject.org/wiki/XInFC7 > > Yes, this is exactly right. We need to be improving autoconfiguration > instead of relying on that display module more. If anyone is having > problems with the autoconfig results, please file bugs about it. This > stuff is still a little rough around the edges, particularly in the > kickstart case (yet another thing on my todo list...) > > - Chris This is a right direction to go -- but what about situations where it just can't work? For example, in the electronic classroom configuration where I teach, the video output from the podium PC goes to a video splitter which drives an LCD panel and an LCD projector. Each of those devices has an optimal/native resolution, but the splitter prevents the use of DDC to get the monitor specs (and rightly so, because the devices may have different specs). The XInFC7 wiki page just says that we need to be able to remember/bind EDIDs, but there are many cases like this where we won't *get* an EDID at all, ever, and defaulting to the lowest common denominator is "decidedly suboptimal". We can't switch entirely to autoconfiguration. -Chris -- fedora-devel-list mailing list fedora-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-devel-list
