I've got a situation where the callback for an urb fires which wakes up a user process which checks the urb status and finds that it's zero.
But the next time the user process tries to submit the urb usb_submit_urb() returns -ENODEV becaus urb->dev is NULL. How is a driver supposed to determine that the USB subsystem is actually done with an URB? I can't believe that it has to do something like poll urb->dev... --gmcnutt _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
