Am Samstag, 1. Mai 2004 17:15 schrieb Alan Stern:
> Instead they can be used by the hub driver to ensure that only one thing
> happens on a hub at any time. When suspending or resetting a port, the
> rule should be to acquire the serialize lock on the child first, then on
> its parent hub. That matches the requirements of usb_reset_device(), and
> the new suspend code can easily be changed to comply.
But usb_reset_device() can lead to a topology change.
Regards
Oliver
-------------------------------------------------------
This SF.Net email is sponsored by: Oracle 10g
Get certified on the hottest thing ever to hit the market... Oracle 10g.
Take an Oracle 10g class now, and we'll give you the exam FREE.
http://ads.osdn.com/?ad_id=3149&alloc_id=8166&op=click
_______________________________________________
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
