On Fri, 12 Dec 2003, Oliver Neukum wrote: > Not so simple. Khubd goes down a list. If the first item on its list > is not your failed reset, a deadlock will occur. > > After you have submitted the URB that really does the reset, you > are commited. You must either set a valid address or disable the port. > You can rely on nobody else to do that.
I think we agree on that. It was never my intention that fixing up a failure between the port reset and setting the device address should be put off for later handling by khubd. That would be done immediately. Hoever the consequent changes to the device structure (i.e., everything needed to reflect the fact that it is disconnected) could be done in another thread. Alan Stern ------------------------------------------------------- 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
