Am Freitag, 2. Januar 2004 18:52 schrieb David Brownell:
> Oliver Neukum wrote:
>
> > - in error recovery by disabling ports we should (currently don't - but
> > that's a bug) go _up_ the tree.
>
> Why would that be? If code has a valid lock on a hub, to disable
> or reset a port on that hub, why would it get a lock on the
> parent of that hub?
If disabling fails, what other choice do you have but go higher
in the tree?
You may try some things, but in the end, if all fails, you'll need
to go up.
Regards
Oliver
-------------------------------------------------------
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
