On Sat, 3 Jul 2004, Stephen J. Gowdy wrote: > You devices entry for the EHCI doesn't look like I'd expect. The one I > have is; > > T: Bus=03 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=480 MxCh= 5 > B: Alloc= 0/800 us ( 0%), #Int= 0, #Iso= 0 > D: Ver= 2.00 Cls=09(hub ) Sub=00 Prot=01 MxPS= 8 #Cfgs= 1 > P: Vendor=0000 ProdID=0000 Rev= 2.04 > S: Manufacturer=Linux 2.4.21-15.0.2.EL ehci-hcd > S: Product=NEC Corporation USB 2.0 > S: SerialNumber=00:0a.2 > C:* #Ifs= 1 Cfg#= 1 Atr=40 MxPwr= 0mA > I: If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub > E: Ad=81(I) Atr=03(Int.) MxPS= 2 Ivl=256ms > > What is in your log files when your usb HCI drivers get loaded and when > you plug in your device? Does /proc/interupts increase for the line with > ehci on it? > > On Sun, 4 Jul 2004, Toby Collett wrote: > > > Hi, > > I have a USB device which internally has a USB 2.0 hub with two high > > speed devices attached, i am connecting it to my laptop which has USB > > 2.0 support... > > The problem is that the USB 2 hub in the device allways gets attached to > > one of the UHCI hubs instead of the EHCI root hub. Is there a way to > > force it to attach as USB 2.0 and not fall back to UHCI? > > > > The device works fine in windows at high speed...
Stephen is right, your entry is missing three lines for the Manufacturer, Product, and SerialNumber. To get more information about what's going on, turn on the USB debugging in your kernel's configuration and look at the system log or dmesg output for the time when the ehci-hcd driver is loaded. Alan Stern ------------------------------------------------------- This SF.Net email sponsored by Black Hat Briefings & Training. Attend Black Hat Briefings & Training, Las Vegas July 24-29 - digital self defense, top technical experts, no vendor pitches, unmatched networking opportunities. Visit www.blackhat.com _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-users
