On Sat, 2009-01-17 at 19:03 +0000, Luis Silva wrote: > @scot: If you only have usb 1.0 hardware then ehci-hcd will do nothing. > only when you load uhci-hcd will you have access to those deices. The > point is the ehci-hcd driver does not block the uhci-hcd controlled > devices. But the later drier acts on the USB 2.0 devices and prevents > them from working full speed, even if you load ehci afterwards. > Exactly my point.
If you have to load ehci-hcd before uhci-hcd for the kernel to function properly, but ehci-hcd only has MODALIAS strings for USB 2 devices, then it's the kernel's fault that this doesn't work! If there's a pre-order condition, then these things shouldn't even be considered separate drivers! uhci-hcd/ohci-hcd should depend on the ehci-hcd driver to ensure that it is loaded first. Alternatively they should be just compiled into one single usb-hcd driver that figures it out for itself. A non-modular kernel only fixes this for people who don't compile their own. Scott -- Scott James Remnant [email protected] -- warning: ehci_hcd loaded AFTER uhci_hcd and ohci_hcd https://bugs.launchpad.net/bugs/296710 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
