Am Samstag, 29. Mai 2004 17:23 schrieb Alan Stern:
> However, there's a definite disadvantage to using dev->serialize for this
> purpose: It can delay khubd and disconnect notifications. usb-storage
> can wait for fairly long periods, 20 or 30 seconds sometimes. If it holds
> the serialize semaphore during those times then it will block khubd if the
> device is disconnected.
Why? Won't the transaction fail within the usual time?
> On the whole, it might be better to add a new mutex to struct usb_device
> to provide this sort of driver-level serialization rather than overload
> the existing mutex, which is meant to serialize actions by usbcore.
But we should guard against actions by or through usbcore, too.
If I understand the problem correctly ep 0 must not be touched within
this window, no matter what.
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_id149&alloc_id66&op=click
_______________________________________________
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
