On Fri, 12 Dec 2003, David Brownell wrote:I'd split step 4 into "4a" (device descriptors) and "4b" (config descriptors) ... and then re-factor so 1..4a is the same code as normal khubd enumeration. ...
Sure. Although depending how you do it, step 3 might be different (reuse the old address vs. assign a new address). Also the failure paths will be different. But that could all be handled with proper refactoring.
That logic has always been a bit strange -- picking out the address _before_ it starts the reset/set_address/get_descriptor code. Here's where that strangeness actually helps ... :)
That would also reduce the length of time the address0_sem is held,
It would? How so?
It would be dropped after the address is assigned (the bus no longer has an "address zero") ... rather than waiting until after the device was configured and all its interfaces were probed. I think that's the issue Oliver alluded to in his followup to your comment.
- 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
