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
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 writ
On Thu, 17 Aug 2006, Lonnie Mendez wrote:
> 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
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 mess
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
