> Seems like at one point I saw a STALLd control transaction return the > urb with status -EPIPE. But right now I'm seeing a case where I submit a > control read, which is STALLd, but the urb's callback isn't being > invoked.
Sounds like a probable host controller driver bug to me... > What's should I expect when the device STALLs a control read? How do I > detect this condition so I can unlink the urb? Hmm, as I understand it devices are allowed to report "protocol stalls" for cases like "device doesn't implement that control request". BUT they're not allowed to actually halt a control endpoint ... in fact, control requests must always get through. You shouldn't need to unlink anything. "-EPIPE" is just a normal response that gets delivered to your driver's completion function when the control URB is unlinked. Once you see that report, there should be no further record in usbcore that it happened. - Dave _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
