Hi,
I have two machines running 2.4.19-UP, one with v1.0 UHCI ports, and the
other with v1.1 OHCI. I also have a USB device that has an experimental
driver. I have discovered that when I load the USB device's driver and
try to
$ cat /proc/bus/usb/devices
on the UHCI machine, then Linux will "hang" for a few seconds before it
(presumably) times out and prints the descriptor for the experimental
device. After this, the device has effectively been clobbered and must
be reset. However, it all works fine if I examine /proc/bus/usb/devices
*before* loading the driver.
I can read /proc/bus/usb/devices successfully on the OHCI machine,
regardless of whether the driver is loaded or not. However, I haven't
been able to activate the device on this machine yet (although it *is*
recognised) and so maybe this has something to do with it? I am using
the same version of the driver on both machines.
Can anybody think of a reason why reading /proc/bus/usb/devices would
"hang" a UHCI controller? I strongly suspect a driver bug because other
devices have no such problem, but where would such a bug be most likely
to be?
Thanks for any advice,
Cheers,
Chris
-------------------------------------------------------
This sf.net email is sponsored by:
Access Your PC Securely with GoToMyPC. Try Free Now
https://www.gotomypc.com/s/OSND/DD
_______________________________________________
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-users
