Hello Peter,
many many thanks for your long and detailed answer.
On the protocol design:
First, using CDC-ACM means sacrificing all structured communication
offered by the USB packet bus and settling for such primitive use of
USB is not a decision that should be made lightly. Almost all
Hello Peter,
one short remark
Application-specific or vendor-specific are often frowned upon in
other contexts but if the protocol is documented publically then it
is a great way to take advantage of all that USB offers, and it is
explicitly supported by the specification. Use bDeviceClass
I saw the in the device endpoint ep82/ep83 at wMaxPacketSize a size 0040.
As far as I understand the packet 7092 in wireshark with URB data length 128
should not possible? What happens at such packets sizes? Or does wireshark just
joking me --
To
I saw the in the device endpoint ep82/ep83 at wMaxPacketSize a size 0040.
As far as I understand the packet 7092 in wireshark with URB data
length 128 should not possible? What happens at such packets sizes?
Or does wireshark just joking me --
Wireshark adds 64 bytes of overhead to each
Does my log means it has nothing to do with kernel itself ?
Maybe you're experiencing a problem with link power management. Some
changes were just merged into Greg KH's development tree (the usb-linus
branch), and they should appear in the next 3.14-rc release. You could
try either one of
unsubscribe linux-usb --
To unsubscribe from this list: send the line unsubscribe linux-usb in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
So I am back with more tests on this problem.
Intel itself told us it is a problem on the driver for the XHCI host
controller. I will put some stuff here now what I goo from Intel:
Let me explain why I came back to you with this problem.
We have already tried the same thing with an echo device
+, Kasberger Andreas wrote:
So I am back with more tests on this problem.
Intel itself told us it is a problem on the driver for the XHCI host
controller. I will put some stuff here now what I goo from Intel:
Let me explain why I came back to you with this problem.
We have already tried