better to be explicit I think: provide a routine for halting the endpoint (I guess this exists already). Then people who resubmit in the completion handler can do:
halt the endpoint (all submissions to the endpoint will fail). unlink the urb (synchronously) restart the endpoint
Not all endpoints are haltable in a useful sense. - Isochronous ones don't halt. - Control endpoint halts aren't persistent.
Drivers that resubmit in completion without synchronizing with their own disconnect processing are buggy -- plain and simple. Left hand fighting with right hand.
- Dave
------------------------------------------------------- This SF.net email is sponsored by: IBM Linux Tutorials. Become an expert in LINUX or just sharpen your skills. Sign up for IBM's Free Linux Tutorials. Learn everything from the bash shell to sys admin. Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
