Messages in this thread | | | From | "jeff millar" <> | Subject | Re: [ANNOUNCE] Hardware detection tool 0.2 | Date | Fri, 31 Aug 2001 19:46:38 -0400 |
| |
What bus and slot number does the driver use to register itself before the plugging the card?
----- Original Message ----- From: "Greg KH" <greg@kroah.com> To: "jeff millar" <jeff@wa1hco.mv.com> Cc: "Carlos E Gorges" <carlos@techlinux.com.br>; <linux-kernel@vger.kernel.org> Sent: Friday, August 31, 2001 7:23 PM Subject: Re: [ANNOUNCE] Hardware detection tool 0.2
> On Fri, Aug 31, 2001 at 06:58:59PM -0400, jeff millar wrote: > > > > One reason: Not all hardware has the signals needed to detect when a card > > gets plugged or unplugged. Consider legacy cPCI systems. The don't have > > the Hot Swap extensions or backplane hot swap control. The only way to find > > the cards is to periodically scan the bus for new cards, cards that > > disappeared, or requests for Hot Swap. > > But the driver for those devices have a struct pci_driver object that > they use to register themselves with the PCI subsystem, right? The > MODULE_DEVICE_TABLE uses the id_table structure in the struct pci_driver > object. That's all, it isn't necessarily a hotplug specific thing. > > And having that MODULE_DEVICE_TABLE for those drivers will allow the > kernel to load those modules when the bus is scanned for new cards, like > on boot :) > > thanks, > > greg k-h >
- 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/
| |