> Glenn Burkhardt wrote: > > I've run into a weird one, and if anyone has any ideas, I'd appreciate it. > > > > I'm working with a joystick from CH Products. It works OK when it's connected > > to the system at boot, but not correctly after a hot connect, or a driver > > re-load. The data reported never changes. In fact... > > Does OHCI (or EHCI through a high speed hub) do the same, or is this > just a UHCI bug? > >
I took your advice and bought a 2.0 add on board. It has an NEC 720101 controller, and supports OHCI and EHCI. But the symptoms are the same. It's OK if the joystick is connected at boot, but doesn't hot connect. The report values are latched at whatever value they are at connect time. Putting in an intermediate low speed hub makes no difference, either. My system didn't automatically load the OHCI driver, unless a USB mouse was plugged into the add on card. When the driver is manually loaded after a full boot, the joystick doesn't work, even if it's connected at boot. Mandrake has a hook to load modules prior to the filesystem check and processing entries in fstab. If I use this hook by creating an entry for usb-ohci entry in /etc/modules, and the joystick is connected prior to boot, it works. Thanks for the interest. ------------------------------------------------------- SF.Net is sponsored by: Speed Start Your Linux Apps Now. Build and deploy apps & Web services for Linux with a free DVD software kit from IBM. Click Now! http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
