Thanks Alan,
that was very helpful.
/Bernd
Alan Stern wrote:
On Tue, 14 Jul 2015, Bernd Porr wrote:
I've got a question regarding ISO transfer. If the firmware is not
providing data is the ISO urb returning zero packet length and if yes
how can I check that in the driver? I'm wo
I've got a question regarding ISO transfer. If the firmware is not
providing data is the ISO urb returning zero packet length and if yes
how can I check that in the driver? I'm working on a solution for my
USBDUX driver where the ADC for example takes 800us to measure all data
so that a couple
s Ladisch wrote:
(quoting fixed)
Bernd Porr wrote:
Alan Stern wrote:
On Wed, 24 Jun 2015, Bernd Porr wrote:
I use urb->interval to control the sampling rate of these devices.
That works fine with the ehci driver. When I use the xhci driver it
seems to be interpreting the urb->interval in a
way I can update the firmware for xhci and
test it without causing havoc for those using the drivers just now.
In that way USB 2.0 is untouched and I can write the xhci support which
doesn't work at all at the moment so can only get better.
/Bernd
Alan Stern wrote:
On Wed, 24 Jun 2015, B
Hi all,
I'm the maintainter of the the USBDUX* devices.
They are USB 2.0 high speed devices. I use urb->interval to control the
sampling rate of these devices. That works fine with the ehci driver.
When I use the xhci driver it seems to be interpreting the urb->interval
in a different way and
Hi all,
is that right that setting urb->interval does not work for the xhci
driver? Seems so that the driver (in my case the usbduxsigma.c) needs to
request the xhci_interval and then has to live with that frame rate so
essentially 125us? Is that right?
/Bernd
xhci-ring.c: (I've added a cou
Hi all,
is that right that setting urb->interval does not work for the xhci
driver? Seems so that the driver (in my case the usbduxsigma.c) needs to
request the xhci_interval and then has to live with that frame rate so
essentially 125us? Is that right?
/Bernd
xhci-ring.c: (I've added a cou
