On Mon, Jan 13, 2003 at 06:10:04 -0800, Mark Vojkovich wrote: > On Mon, 13 Jan 2003, Tim Roberts wrote: > > > On Mon, 13 Jan 2003 16:12:21 -0800 (PST), Mark Vojkovich wrote: > > > > >On Mon, 13 Jan 2003, Tim Roberts wrote: > > > > > > [...] > > > > > >> As I recall, there is work going on to eliminate this problem by allowing > > >> our drivers to claim a whole range of PCI IDs, eliminating the need for > > >> xf86PciInfo.h. Is that work present in 4.3.0? > > > > > > xf86PciInfo.h isn't needed. I stopped adding NVIDIA cards to it > > >a while ago. I'm not really sure why we even have an xf86PciInfo.h. > > >The burden supporting a particular device ID is, and I believe always > > >has been, in the driver. Merely adding a PCI ID to xf86PciInfo.h > > >doesn't add support for that PCI ID. > > > > What you say is true, EXCEPT for "XFree86 -configure". At least as late as > > 4.2.1, the automatic configuration stuff will refuse to run if the PCI id is > > not in xf86PciIfno.h. > > > > Does your nv hack solve that? > > > > I don't know anything about "-configure". And I can't put PCI IDs > in xf86PciInfo.h if I don't know what they are. The point of my nv > hack was to support cards that haven't come out yet.
Don't worry about -configure now. When 4.3.0 ships, it no longer requires the information in xf86PciInfo.h Alan. _______________________________________________ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
