Here's the message I sent to Georg earlier today. Forgot to hit "reply to
all"... think I'm getting Alzheimer's or something...
----- Original Message -----
From: "..tom" <[EMAIL PROTECTED]>
To: "Georg Acher" <[EMAIL PROTECTED]>
Sent: Sunday, April 30, 2000 1:35 PM
Subject: Re: [linux-usb] Re: One-shot interrupts with usb-uhci
> From: "Georg Acher" <[EMAIL PROTECTED]>
>
> > Hm, when you submit an interrupt with an interval of zero, it is
supposed
> > to do a one-shot-interrupt. Whether the urb is then automatically
> unlinked, is
> > another issue (was there a consensus lately?). To officially stop an
> ongoing
> > interrupt, you should issue usb_unlink_urb().
>
> I haven't tried that one yet. The situation I have here is that I want to
> start an interrupt for a number of transfers, then stop it (from within a
> completion handler). My luck with usb_unlink_urb has been, well, not too
> nice. If I *don't* set the asynchronous unlink flag, it comes back with 0,
> but doesn't unlink. If I do set the asynchronous unlink flag (as I
should),
> it oopses nicely - chances are that this is caused by me trying to
re-start
> the interrupt cycle afresh.
>
> I have decided that it is cleaner for my particular application to submit
> the urb, have the transfer going on, and when I need to stop it, return
> interval=0. Works with JE usb, and (after the patch I sent out yesterday)
> with AFS usb-uhci as well. I'll try the usb_unlink_urb() again when I get
> back to the machine with the code on it...
>
> Thanks for the info,
> ..tom
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
