On Fri, 2016-09-16 at 18:24 +0200, Julio Guerra wrote:
> > On Sat, 2016-08-20 at 14:14 +0200, Julio Guerra wrote:
> Another example:
> > 00 00 00 00 00 00 00 01
> ...
> > 01 00 00 00 00 00 00 00
> ...
> > 00 01 00 00 00 00 00 00
> ...
> > 00 00 01 00 00 00 00 00
> On Sat, 2016-08-20 at 14:14 +0200, Julio Guerra wrote:
Another example:
> 00 00 00 00 00 00 00 01
...
> 01 00 00 00 00 00 00 00
...
> 00 01 00 00 00 00 00 00
...
> 00 00 01 00 00 00 00 00
after a random number of times, while usbmon shows the usb payload
On Sat, 2016-08-20 at 14:14 +0200, Julio Guerra wrote:
> >> Another example:
> >>> 00 00 00 00 00 00 00 01
> >> ...
> >>> 01 00 00 00 00 00 00 00
> >> ...
> >>> 00 01 00 00 00 00 00 00
> >> ...
> >>> 00 00 01 00 00 00 00 00
> >> after a random number of times, while usbmon shows the usb payload
>
>>> Another example:
00 00 00 00 00 00 00 01
>>> ...
01 00 00 00 00 00 00 00
>>> ...
00 01 00 00 00 00 00 00
>>> ...
00 00 01 00 00 00 00 00
>>> after a random number of times, while usbmon shows the usb payload
>>> "00 00 00 00 00 00 00 01".
>>
>> Hi, how many bytes does
>> Another example:
>>> 00 00 00 00 00 00 00 01
>> ...
>>> 01 00 00 00 00 00 00 00
>> ...
>>> 00 01 00 00 00 00 00 00
>> ...
>>> 00 00 01 00 00 00 00 00
>> after a random number of times, while usbmon shows the usb payload
>> "00 00 00 00 00 00 00 01".
>
> Hi, how many bytes does read() return?
>
On Sat, 2016-08-20 at 05:40 +0200, Julio Guerra wrote:
> Another example:
> > 00 00 00 00 00 00 00 01
> ...
> > 01 00 00 00 00 00 00 00
> ...
> > 00 01 00 00 00 00 00 00
> ...
> > 00 00 01 00 00 00 00 00
> after a random number of times, while usbmon shows the usb payload
> "00 00 00 00 00 00 00
Hi,
I have noticed a problem using a usb device managed by the cdc_acm
driver. The data received from the device and copied to userspace ends
up being shifted by one byte again and again after some amount of calls
to read() and most importantly with previously read data. usbmon shows
the usb data