On 06/17/2010 09:41 PM, Stephen Warren wrote:
On 06/17/2010 08:24 AM, Alan Stern wrote:
On Wed, 16 Jun 2010, Stephen Warren wrote:
Adding the msleep() works! ...
You should first find out how long the delay needs to be...
It looks like 200ms is the magic value...
All right. We could add a quirk indicating that the device needs a
delay before the Get-Device-Qualifier call. I don't like the idea of
adding an unconditional delay; enumeration already takes too long.
Or more simply, we could add a quirk indicating that the kernel
shouldn't issue the Get-Device-Qualifier call at all. The only reason
it's there is for printing a message in the log when a
high-speed-capable device isn't plugged into a high-speed port.
I tested the sleep on a second laptop and it seems to work fine there too.
I also tested using the congruity/libconcord application against the
remote, and the previous problems (re-enumerating the remote after
upgrading its configuration and resetting it) are also fixed.
So, I'd call this fix/hack/workaround fully tested from my side.
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html