> So the question is, how do you add PCI IDs to a module which isn't
> loaded?
I think the key is here, in drivers/pci/pci-driver.c:
/**
* pci_register_driver - register a new pci driver
* @drv: the driver structure to register
*
* Adds the driver structure to the list of registered drivers
* Returns the number of pci devices which were claimed by the driver
* during registration. The driver remains registered even if the
* return value is zero.
*/
int
pci_register_driver(struct pci_driver *drv)
So it's perfectly legal to have a driver loaded, for which no device
instances are present. Then you can add the new ID, and it gets probed
for automatically. When I was testing this, I had the e100 driver built
in statically, and though it didn't have the ID for my actual device in
the table, it remained available. When I used the new_id interface to
add the ID, then it probed for devices again, the new ID matched, and it
attached itself to the hardware instance.
Granted, today not all the drivers do this. But I think it's part of
the grand hotplug scheme to allow them to do so.
This does also mean that a whole pile of drivers, for which hardware may
*never* be present, could be loaded. My sysfs tree shows drivers for
several PCI devices, which I left as =y in my .config file, which don't
exist in my system.
I'll be out of touch the next few days, but will join back in any
discussion next week.
Thanks,
Matt
-- Matt Domsch Sr. Software Engineer, Lead Engineer, Architect Dell Linux Solutions www.dell.com/linux Linux on Dell mailing lists @ http://lists.us.dell.com- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Fri May 23 2003 - 22:00:53 EST