On Friday 02 January 2004 10:24, James_chen\(陳彥宏\) wrote: > first time to fill the URB and send off: > 1. fill URB1 > 2. send off URB1 > > then > 3. fill the same URB, ie. URB1(violate previous URB1 if URB1 does not > complete)
URBs always complete. If you modify an URB after submission and before the completion handler is called than you will be punished :) > 4. send off URB1 again.(Even use spin-lock to protect URB1, the URB1 has > violated at step 3). > > So I think the sequece is: > 1. acquire spin-lock to protect URB1 > 2. fill URB1 > 3. send off URB1 > 4. if URB1 complete, release spin-lock > > Is my idea right? No. The spinlock is for the usb core, drivers shouldn't touch it. All the best, Duncan. ------------------------------------------------------- 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
