Hi, > hotplug walks sysfs. > You can see how it does it by looking at usb_boot_events() in > /etc/hotplug/usb.rc.
I see. I am going to take a look at that tomorrow. >>option, or alternatively, trying to find an ehci controller that is >>paired with the controller currently being initialized before loading >>USB device drivers. > I still cannot understand either of your proposals. The basic problem is that the drivers for the individual devices are loaded before it is clear whether the host controller they hang off is a 1.1 or a 2.0 controller. This means they are enumerated twice, once for 1.1 and once for 2.0. Loading the 2.0 driver generates removal events for the 1.1 devices, so there is no logical error, however it slows down the boot process a lot because the drivers have to be loaded twice. ATM I can still only stab at the problem -- it is late and I'm going to jump onto a train the next minutes, however I think it ought to be possible in some way to make sure that before a device is initialized it is connected to the "right" host controller. I can think of two "simple" ways: try to load ohci, uhci and ehci first, then go looking for USB devices, or postpone initializing 2.0 devices until USB setup is finished. I think I'm going to follow up when I have looked at it more deeply. Simon -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
