Hello Alan, > It sounds like you are concerned about serializing interrupt messages > with control messages.
No. If I only send control messages from the INT IN completion handler, all is fine. The problem occurs if I send two control messages at the same time, one from user context, one from interrupt context. > In general, if usb_control_msg() returns -EPIPE it's because the > device responded to the control message with a STALL, not because of > any internal synchronization problem in the core or HCD. So I will do a bus trace. This should be easy: the effect is reproducable. > If the device really does have requirements for relative timing of > interrupt and control messages No. best regards Wolfgang Mües ------------------------------------------------------- This SF.Net email is sponsored by: Oracle 10g Get certified on the hottest thing ever to hit the market... Oracle 10g. Take an Oracle 10g class now, and we'll give you the exam FREE. http://ads.osdn.com/?ad_id149&alloc_id66&op=click _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
