> ENXIO errors are unique to the UHCI drivers in all 2.4 and 2.5 upto
> 2.5.43 (?). It's because the UHCI driver's didn't allow queued
> Control URBs, and when you get that some other driver has a URB in
> progress on the DCP.
>
> Find out what other driver is talking to your device. Keep in mind
> that the initial driver binding process can many seconds (I think
> there is a 2 or 3 second sleep in the hotplug script...).
>
> Or, try the latest 2.5 kernel, it should work great.
That is not a satisfactory answer. A device may have several
interfaces, which may all legitimately send control requests at
the same time. Returning ENXIO is simply a bug under these
circumstances.
Now the correct fix would be to backport the 2.5 UHCI driver.
Failing that, usbcore must retry on ENXIO.
While we are at it, how about a complete backport?
Regards
Oliver
-------------------------------------------------------
This sf.net email is sponsored by:
With Great Power, Comes Great Responsibility
Learn to use your power at OSDN's High Performance Computing Channel
http://hpc.devchannel.org/
_______________________________________________
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
