> [EMAIL PROTECTED] wrote:
>
> >>More details needed ... like, which HCD, does this repeat
> >>with different HCDs, and what do you mean by "outbound"?
> >>
> >
> >
> > Sorry. uhci. I haven't tried ohci.
>
> Then try "usb-uhci" to see if it behaves differently.
I am using usb-uhci (lazy f
[EMAIL PROTECTED] wrote:
More details needed ... like, which HCD, does this repeat
with different HCDs, and what do you mean by "outbound"?
Sorry. uhci. I haven't tried ohci.
Then try "usb-uhci" to see if it behaves differently.
Outbound means from the host to the device, to endpoint 0, us
On 5 Jun 2003 at 11:27, David Brownell wrote:
> [EMAIL PROTECTED] wrote:
> > Writing a device driver for a vendor interface. 2.4.20 kernel.
> > This device has only an interrupt in endpoint plus the control
> > endpoints.
> >
> > When I submit an outbound control urb, the data goes to the dev
[EMAIL PROTECTED] wrote:
Writing a device driver for a vendor interface. 2.4.20 kernel. This
device has only an interrupt in endpoint plus the control endpoints.
When I submit an outbound control urb, the data goes to the device,
but the completion handler is never called. If I submit an ur
Writing a device driver for a vendor interface. 2.4.20 kernel. This
device has only an interrupt in endpoint plus the control endpoints.
When I submit an outbound control urb, the data goes to the device,
but the completion handler is never called. If I submit an urb with
an error, like an
