On Tue, 3 Jan 2006 15:46:31 -0500 (EST), Alan Stern <[EMAIL PROTECTED]> wrote:
> > Now the _very_ old treatment was to retransmit with an error message. > > Is this what you mean? > > I was talking about intr-OUT and control transfers; you're right that > intr-IN transfers do get retried. I see, sorry. Yes, I tend to forget about them because they cannot cause a soft-lockup. > I submitted something similar, as you may recall, so I'm certainly open to > the idea of more sophisticated error handling. Possibilities include > backoff-and-retry and port reset. David is right about the timer. But I was under some constraints to implement a fix in RHEL with a minimal risk... A timer introduces some risk of improper locking, events lost, or some double-resubmit. Needs some careful coding and I am often inattentive. Would you scope an implementation? Then I can steal it for RH ;-) -- Pete ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click _______________________________________________ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
