David Dawes <[EMAIL PROTECTED]> wrote: > >How does this affect installable modules such as our drivers (soon to be > >released) that can support multiple chipsets that are already supported > >by existing driver modules? The same would go for NVIDIA, ATI and Matrox > >binary only drivers - how would they be handled? > > What we're doing here will still handle 3rd party modules. At a > minimum there will be an editable mapping between hardware and > driver modules. That mapping won't be hard-coded into the XFree86 > server (although some generic fallback might). In your case, where > one driver handles everything, the mapping would be trivial.
Sounds good. So I assume this will probably be just a PCI->driver type mapping for PCI/AGP devices (and something else for older non-PCI stuff)? > In the 4.x time frame, the XF86Config file won't disappear (just > not be required), and it (or some equivalent) will always be needed > to store configuration preference information. Sounds good to me. The XF86Config file has always been a bit of a nightmare for non-techies to edit anyway ;-) Regards, --- Kendall Bennett Chief Executive Officer SciTech Software, Inc. Phone: (530) 894 8400 http://www.scitechsoft.com ~ SciTech SNAP - The future of device driver technology! ~ _______________________________________________ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
