> A common issue for them is the availablility of a version of usb_control_msg > that is asynchronous (or at least, can be called in interrupt context). > ... > > catc.c has an interesting model that basically queues messages. Maybe > something along those lines could be added to the usb core code as either a > macro or a helper routine.
Could you clarify how that'd be different from just submitting a control URB, without blocking until it completes? I understand that the UHCIs seem to disallow queueing of such URBs, which IMO should be fixed. - Dave _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
