On 16/03/2013 10:15 PM, Greg KH wrote:
Look at the data on the wire, and notice all of the delay and gaps that
could have been filled with real data, but the protocol involved here
(the "old" usb storage spec) prevents the full use of the xhci
controller.
Now if you actually were able to keep th
On 16/03/2013 09:44 PM, Greg KH wrote:
I'm guessing here that you aren't talking about Linux.
My question is not related to Linux. It's related to xhci, and I asked
on this mailing list because it's a public list with people experienced
in xhci.
The question is: what possible scenario could
I'm writing a kernel driver for xhci. USB3 is used mainly for
high-performance external disk drives.
The driver receives a memory buffer to do DMA from (or to.) Buffer can
come from either user-land or kernel-land. So driver can't be sure the
buffer is mapped into kernel virtual address-space
