On Fri, Jul 03, 2015 at 10:03:22AM -0400, Alan Stern wrote:
> On Fri, 3 Jul 2015, Peter Chen wrote:
>
> > According to the USB 2.0 Spec CH5.5.3 and CH8.5.3.2, only control
> > read (IN) needs zero length packet.
> >
> > Cc: Alan Stern
> > Signed-off-by: Peter Chen
> > ---
> > drivers/usb/gadge
Hi,
On Sun, Jul 05, 2015 at 06:56:29PM +0200, Paul Jones wrote:
> Ricardo,
>
> I’m trying to get the 3380 to work in UAS mode on the 4.0.1 and/or 4.1.0-rc8
> kernels.
> I’m using the following script (derived from Sebastian’s post):
> modprobe tcm_usb_gadget
> mount -t configfs none
Alan Stern wrote:
Is 0u the wrong thing to do?
It depends on what you want. If you want complete details (all the
packets, all the data) then you need to use the binary interface,
i.e., wireshark or dumpcap.
But if it helps to know that roughly one packet in every four is
received with lengt
Ricardo,
I’m trying to get the 3380 to work in UAS mode on the 4.0.1 and/or 4.1.0-rc8
kernels.
I’m using the following script (derived from Sebastian’s post):
modprobe tcm_usb_gadget
mount -t configfs none /sys/kernel/config
CONFIGFS=/sys/kernel/config/
TARGET=$CO
On Sat, 4 Jul 2015, Andy Furniss wrote:
> Ok, so I found https://www.kernel.org/doc/Documentation/usb/usbmon.txt
>
> I temporally re-enabled xhci and managed to get a dump with
>
> cat /sys/kernel/debug/usb/usbmon/0u >
>
> I notice it doesn't show data counts - only the first 5 out of 64 x
Alan Stern wrote:
By comparing the arrival times of the packets. usbmon will tell you
exactly which microframe an isochronous packet was scheduled for, if
you understand its output. If there are any gaps in the isochronous
stream, you'll be able to see them.
Ok, so I found https://www.kernel
When sending lots of small packets, this patch will generate an "Unable to
handle kernel paging request" in the memset call:
ndp16 = memset(ctx->delayed_ndp16, 0, ctx->max_ndp_size);
And I don't know why.
Any comment or suggestion would be greatly apreciated.
This has been reproduced in a QEMU X8
[1.] One line summary of the problem:
ch341 module fails on 4.1.1 kernel
[2.] Full description of the problem/report:
It's not possible to work with Arduino board after installing 4.1.1.
ch341 fails and does not create /dev/ttyUSB0 (or /dev/ttyACM0) entry.
On 3.18 and 4.0.0 all was ok.
[3.] Keywo
