> > I've been searching and trying to figure out how to do a single interupt > > out. Does anyone have a snippet of code that I might use that will fill > > an interupt out urb, submit it, wait for a response and then return? And I thought I was the only person who ever tried Interrupt Out (last summer/fall, IIRC, back in the 2.3.99 days). > Simplest is to just have the completion handler unlink the urb > (asynchronously, natch) and submit it like any other interrupt urb. That's the theory, at least. I haven't tried recently, but in 2.3.99 days, this just didn't work right. One of the UHCI HCD's (can't remember which one) allowed to stop the interrupt from being re-submitted if you set bInterval to 0, if my memory serves me right. OHCI definitly didn't allow this, and the other UHCI didn't allow it either. I tried with asynchronous unlink, but never managed to get it working properly. Since I had to ship an embedded app, and I had no choice as far as waiting for an official fix, I went ahead and used the "set bInterval to 0 in completion routine stops URB from being resubmitted". It might even be that I patched the HCD to behave like this. Worked like a charm for this application... I haven't bothered checking again due to other tasks, but might need to get back to this subject again sometime soon. I'd be interested to hear what the official and working way of doing one-shot interrupt out is. Here are two of my old posts which explain things a bit better: http://www.geocrawler.com/archives/3/2571/2000/7/0/4005253/ http://www.geocrawler.com/archives/3/2571/2000/6/0/3966384/ Hope this helps, ..tom _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: http://lists.sourceforge.net/lists/listinfo/linux-usb-devel
