On Wed, 2006-08-16 at 23:17 -0500, Mike Isely wrote: > From: Mike Isely <[EMAIL PROTECTED]> > > When receiving a fatal error from the USB core, e.g. EILSEQ (which can > happen if the polling interval is too short), fail gracefully. > Previously the driver would fill the log with useless error messages > or (more alarmingly) silently spin forever trying to write updated > control information to the device. This change implements a new flag > which if cleared indicates that the driver has failed. The flag will > be set on initialization, cleared on fatal errors, and anything else > that touches the USB port in the driver will abort if the flag is > clear. When the flag is cleared, a message will be logged indicating > that the driver has failed.
I'm not sure how it could spin infinitely grabbing or fetching the internal serial information. Three tries are attempted in cypress_serial_control() before exiting unless other conditions are met. Signed-off-by: Lonnie Mendez <[EMAIL PROTECTED]> ------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
