On Sat, 24 Sep 2005, Chuck Ebbert wrote: > In-Reply-To: <[EMAIL PROTECTED]> > > On Fri, 23 Sep 2005 at 22:12:54 -0400, Alan Stern wrote: > > > The presence of the OHCI driver shouldn't make any difference to how the > > EHCI controller behaves. You could try re-enabling OHCI in your .config > > and recompiling again. Maybe everything will continue to work perfectly. > > You should know better than that. :)
Well, sometimes it does the trick... > 2.6.14-rc2 config with OHCI: > > CONFIG_USB_ARCH_HAS_HCD=y > CONFIG_USB_ARCH_HAS_OHCI=y > CONFIG_USB=y > CONFIG_USB_DEBUG=y > CONFIG_USB_DEVICEFS=y > CONFIG_USB_EHCI_HCD=y > CONFIG_USB_EHCI_ROOT_HUB_TT=y > CONFIG_USB_OHCI_HCD=y > CONFIG_USB_OHCI_LITTLE_ENDIAN=y > CONFIG_USB_STORAGE=y > CONFIG_USB_HID=y > CONFIG_USB_HIDINPUT=y > CONFIG_USB_HIDDEV=y > CONFIG_USB_SERIAL=y > CONFIG_USB_SERIAL_CONSOLE=y > CONFIG_USB_SERIAL_MCT_U232=y Have you tried building these things as modules instead of compiling them into the kernel? Then you could test what happens when you simply rmmod ohci_hcd. > Hotplug USB 2.0 hub -- only OHCI sees it: > > hub 2-0:1.0: state 5 ports 4 chg 0000 evt 0004 > ohci_hcd 0000:00:13.0: GetStatus roothub.portstatus [1] = 0x00010101 CSC PPS > CCS > hub 2-0:1.0: port 2, status 0101, change 0001, 12 Mb/s > hub 2-0:1.0: debounce: port 2: total 100ms stable 100ms status 0x101 > ohci_hcd 0000:00:13.0: GetStatus roothub.portstatus [1] = 0x00100103 PRSC PPS > PES CCS > usb 2-2: new full speed USB device using ohci_hcd and address 2 > ohci_hcd 0000:00:13.0: GetStatus roothub.portstatus [1] = 0x00100103 PRSC PPS > PES CCS > usb 2-2: not running at top speed; connect to a high speed hub > usb 2-2: default language 0x0409 > usb 2-2: new device strings: Mfr=0, Product=1, SerialNumber=0 > usb 2-2: Product: USB2.0 Hub > usb 2-2: hotplug > usb 2-2: adding 2-2:1.0 (config #1, interface 0) Actually none of these messages are relevant. The ones that matter are the ones from ehci_hcd that precede these, especially the one about "full speed --> companion". Unless there _are_ no messages from ehci_hcd -- that would be even more significant. > Remove these two lines, recompile and reboot: > > -CONFIG_USB_OHCI_HCD=y > -CONFIG_USB_OHCI_LITTLE_ENDIAN=y > > > Connect same hub to same port -- now EHCI sees it: > > hub 1-0:1.0: state 5 ports 8 chg 0000 evt 0008 > ehci_hcd 0000:00:13.2: GetStatus port 3 status 001803 POWER sig=j CSC CONNECT > hub 1-0:1.0: port 3, status 0501, change 0001, 480 Mb/s > hub 1-0:1.0: debounce: port 3: total 100ms stable 100ms status 0x501 > ehci_hcd 0000:00:13.2: port 3 high speed This last line here is the important one. The fact that it doesn't say "high speed" when ohci_hcd is present means that you've got some sort of hardware problem. The settings of the OHCI controller are somehow interfering with the proper operation of the EHCI controller. Alan Stern ------------------------------------------------------- SF.Net email is sponsored by: Tame your development challenges with Apache's Geronimo App Server. Download it for free - -and be entered to win a 42" plasma tv or your very own Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php _______________________________________________ [email protected] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
