[PATCH] iso pipe support for usbatm
rkagan at mail.ru
Tue Mar 22 15:41:42 EST 2005
On Sun, Mar 20, 2005 at 06:30:45PM +0100, matthieu castet wrote:
> matthieu castet wrote:
> >matthieu castet wrote:
> >>When I loged the data, I saw there are EOVERFLOW errors. And because
> >>the errors aren't catch by usbatm, the bad packet go through
> >>usbatm_extract_cells and produce the vpi/vci error.
> >>I will try with a smaller size.
EOVERFLOW is reported when there was a babble (out-of-frame activity) on
the usb bus. Another indication of a hardware/firmware problem... Did
smaller buffer size help? And BTW were you talking of bulk or iso
> >In case of error : status !=0 couldn't we add the buffer to the
> >spare_receive_buffers list ?
> or at least set buf->filled_cells to 0.
I thought urb->actual_length represented the amount of successfully
transferred data, i.e. in case of fatal error, 0. Thus ->filled_cells
would be set appropriately, so urb->status can be ignored. I'll go
recheck if this is true with the current hcd code.
More information about the Usbatm