On 20 May 2002, Roger wrote: > > > > > > To note (you reminded me of something), the module ehci-hcd is not being > > > shown as being used by the usb-ohci modules. > > > > It is not used _by_ this module. > > Correction. it is ;-)
I repeat - it is not used _by_ this module. USB2 hardware provides two independent devices - one USB2 and one USB1.x. Just get a look in logs you have shown - you will see two functions on PCI card. One is USB2 and one is USB 1.x > i even tested cd-rw burn rates to make sure. > Burn rates for a without the ehci-hcd module being loaded was ~8x's. > Burn rates with the ehci-hcd module loaded showed ~25x's > So what? You seem to enjoy in making wrong conclusions. The fact that both USB drivers work does not in any way prove that one of them depends on another. > The ehci-hcd will register itself as "not being used by any other > module" and it will work transperantly. > > The following file has more info: > /usr/src/linux/Documentation/usb/ehci.txt > You do not seem to have really understood this document. > > > that ehci-hcd.o is being used by the usb-ohci module so it doesn't > > > unload this, as such, everything hangs. I'll test my theory when i get > > > my next chance to reboot (later this evening sometime). > > Ah Ha! my theory worked. the /etc/rc.d/init.d/pcmcia script is checking > & unloading all drivers that are listed to be registered with the > pcmcia_core/ds modules. (i believe the $PCIC variable within > the script is responsable for unloading these modules.) > USB PCI drivers are not PCMCIA drivers!!! > > I'm thinking the reason the maintainer of the ehci-hcd choose "not to show the > module as being registered" with any other usb module" as it may have caused > a conflict with being able to fall-back to the older usb-ohci/usb-uhci > driver. Just a complete guess here tho. > [...] > well, I've finished recompiling but i don't think i'll need to do that unless > we want to recompile the ehci-hcd module to show itself as being registered and > see what happens form there. > > > As you wish. _I_ want to have debug output so instead of _guessing_ what happens we have some evidence. It looks like you are not interseted in having this bug fixed. It is your choice. In this case you may just as well spare time and bandwidth. You obviously are content with workaround for your personal system. I tried to find a way to fix it for all others. Our goals seem to not agree :-) Unless I see some real debugging information I stop participating in this useless thread. Sorry. -andrej
