On Thu, May 13, 2004 at 12:23:22PM -0400, Alan Stern wrote: > > That bug report mentions kernel 2.6.4. Is the problem still present in > 2.6.6? The best approach is to fix the problem with resume, not to try > and clean up when it fails.
I beg to differ here. No driver should ever dead-lock just because the interrupts stop flowing for whatever reason. > > I've updated my async removal patch for 2.6.6. > > The way your patch works is incorrect. Anyway, that whole section of the > driver is slated for revamping -- when I have enough time to work on it! Sure. As long as you tell me what's wrong with it. > If you rewrite your patch to use a timer (with a 2 ms minimum delay) > instead of a tasklet, I will consider adding it as a stopgap until the > driver is reworked. Why is the delay necessary? Cheers, -- Debian GNU/Linux 3.0 is out! ( http://www.debian.org/ ) Email: Herbert Xu ~{PmV>HI~} <[EMAIL PROTECTED]> Home Page: http://gondor.apana.org.au/~herbert/ PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt ------------------------------------------------------- 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
