On Mon, Feb 26, 2007 at 05:14:38PM -0500, Jon Smirl wrote: > On 2/26/07, Alan Stern <[EMAIL PROTECTED]> wrote: > >> Another way to control this would be to put all of the USB Host IDs > >> into a single module (usbcore), and then that module would load in > >> ehci, uhci, etc. > > > >That would work. But it would be a lot of effort for not much advantage. > > It's not that much work. Just move the PCI device tables form the tree > controller modules into USB core. Then when USB core is probed, find > the device in the table, load the right module and pass the probe on.
But why in the world would we care? These busses can come and go in any number of varied and different ways. If you try to rely on a bus id then you are going to be wrong eventually. Just do not do it, it's wrong and we will not try to work around it in the usb core at all. Use a tool in userspace to handle all of this, like udev, which is exactly what it was created for. Remember, bioses like to renumber PCI device ids all the time too, so don't try to rely on those numbers either. thanks, greg k-h ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
