On Wed, 19 May 2004, David Brownell wrote: > Point being that there's some time, not much more than 1/4 sec > after the "failing" operation starts, where we should know > that either (a) some subtree was disconnected and that's why > we're failing, or else (b) there wasn't a disconnect, so we're > failing for some other reason.
Yes -- except for the single-thread issue. > > I'm thinking the only way to make this work is to delay sending that ALERT > > message for a second or so, to avoid false alarms. Maybe that counts as a > > partial state machine. > > Although if you're resetting a device/port that's already been > enumerated, and its hub gets disconnected, then the hub status > IRQ would certainly have been able to mark the hub NOTATTACHED > earlier than that. 1 second, 1/4 second -- who's counting? :-) Alan Stern ------------------------------------------------------- This SF.Net email is sponsored by: SourceForge.net Broadband Sign-up now for SourceForge Broadband and get the fastest 6.0/768 connection for only $19.95/mo for the first 3 months! http://ads.osdn.com/?ad_id=2562&alloc_id=6184&op=click _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
