> > I'd not attempt such tricks outside the completion handler, though.
> > And it shouldn't really be necessary, either. ISO will have the same
> > issue; in both cases, a fix seems like it'd need to formally introduce
>
> Why? An ISO URB is in progress or done when its completion is called.
>
On Sat, Jun 23, 2001 at 06:43:33AM -0700, David Brownell wrote:
> I'd not attempt such tricks outside the completion handler, though.
> And it shouldn't really be necessary, either. ISO will have the same
> issue; in both cases, a fix seems like it'd need to formally introduce
Why? An ISO URB
> The OHCI driver only seems to want to actively unlink an URB if it's
> status is -EINPROGRESS. The status of an interrupt URB in the completion
> handler is 0. I've managed to get the USB sub-system to unlink the URB by
> setting status to -EINPROGRESS. I know this is naughty but so far I
> h
> From: Michael Bosland <[EMAIL PROTECTED]>
> To: [EMAIL PROTECTED]
> Date: Fri, 22 Jun 2001 15:03:01 -0700 (PDT)
> The OHCI driver only seems to want to actively unlink an URB if it's
> status is -EINPROGRESS. The status of an interrupt URB in the completion
> handler is 0. I've managed to get
Hi,
I'm still working on Interrupt Out communications. I think I may have
found a work around for my problem.
The OHCI driver only seems to want to actively unlink an URB if it's
status is -EINPROGRESS. The status of an interrupt URB in the completion
handler is 0. I've managed to get the USB
