Am Montag, 14. M�rz 2005 16:57 schrieb Brian Murphy:
> The best fix I have found so far is to detect if the disconnect function
> is called first
> with the data interface and just return without doing anything, waiting
> to be called
> with the control interface (see attached patch). �This fixes this hang
> and the original
> crash.
Sorry, no. This is impossible. After disconnect() returns, the interface
must not be used any longer. Ignoring disconnect() is not an option.
Regards
Oliver
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_ide95&alloc_id396&op=click
_______________________________________________
[email protected]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
