Let me start by saying this is at least 5 years overdue. Glad to see David addressing this problem.
I would like to suggest that a more aggressive approach be used that would involve (or allow) driver changes. Using external tools to figure out which graphics driver and input devices to use sounds like a fine idea; however, it seems that the driver should be responsible for determining a set of default settings. The driver is in a far better position to detect the monitor. Most drivers on other platforms have built in EDID parsing and methods to detect displays that may not even support such standards (Especially common in embedded market) Additionally the driver knows the availability of mult-display features from flat panel or TV encoders which cannot be determined without extensive hardware probing. This probing is already needed for the driver's operation and could be leveraged for a self-configuration purpose. A would suggest that a driver should initialize by the X server asking (rather than telling) the driver how many screens and what modes are supported. The driver can obtain this information from the XF86Config file when available or via it's own detection. The data is then written back to the XF86Config file at runtime. A runtime configuration (via randr, and additional protocols) would also allow for changing arbitrary display features at runtime and have them written back to the XF86Config file. Autoconfiguration is one overdue item, but runtime configuration is every bit a "required 5 years ago" feature that should be addressed in parallel since they have overlapping needs. -Matt -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of David Dawes Sent: Wednesday, October 01, 2003 3:28 PM To: [EMAIL PROTECTED] Subject: Starting XFree86 without an XF86Config file The first part of the work I'm doing to improve the XFree86 configuration experience for users is now available. Some details about it, and a link to the source patch can be found at <http://www.x-oz.com/autoconfig.html>. The goal of this first stage is to make it possible to start the XFree86 server in a useful and usable form for most users without any prior user intervention. In particular, without first creating an XF86Config file. I'm planning to commit this before the next regular snapshot. The testing so far has been limited to the hardware platforms I have access to. Feedback is welcome. David -- David Dawes X-Oz Technologies www.XFree86.org/~dawes www.x-oz.com _______________________________________________ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel _______________________________________________ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
