On Mon, Apr 11, 2011 at 3:08 PM, Graeme Gill <graeme2@xxxxxxxxxxxxx> wrote: > Xiaofan Chen wrote: >> Hmm, assuming that you are using libusb, I think the issue >> would have gone with later kernels (say 2.6.32 or later). Alan >> Stern has already post a real patch to the kernel after the following >> RFC which was CCed to the libusb mailing list. I think you do not >> need the resetep work-around with later kernels. >> >> http://libusb.6.n5.nabble.com/RFC-Skip-sending-Set-Interface-during-driver-unbinding-td6073.html > > I'm not really seeing the relevance, unless it is to hint that > even my workaround will be broken by latter kernels ? No it is not to hint that your workaround will be broken. > ie. if on recent Linux kernels the resetep IOCTL no longer does anything > (ie. it doesn't reset the data toggle), then it breaks my workaround. > > But perhaps the above reference is not to the resetep IOCTL, but to > the side effect of set interface ? (Set interface doesn't figure in > my problem as far as I can tell.) I see. If the side effect of Set_interface is not the problem with your device, the above reference is not relevant to your issue. > Traces from the Linux USB driver debug didn't seem to reveal anything > interesting - the problematic data read just hangs. I think you can still post it. The Linux USB developers can do wonders with the USBMon logs. :-) -- Xiaofan -- 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
