On Wednesday 10 September 2003 18:16, David Brownell wrote: > Duncan Sands wrote: > > Hi all, in 2.6 a flag is set on device disconnect that causes any > > future urb submissions to fail. Then all pending urbs are "nuked". > > This sounds great (especially if you want to "fire and forget" your > > urbs), but does it actually work? For example, uhci-hcd does not > > seem to implement the disable method, so as far as I can see > > "nuking" doesn't actually do anything much - or am I confused? > > It does force all the URBs to be unlinked. > > But nothing waits for the unlinks to complete. I suppose that if > the HCD doesn't have a disable() method, then hcd_endpoint_disable() > could wait. Though in general I'd rather see the HCDs implement > that method, so clearing out endpoint state isn't accidental. > > > I would like to be confident that urb unlinking in a disconnect > > method is pointless - because the urbs have already been nuked. > > Is that right? > > See above. Until we can rely on HCD being finished with unlinks, > I'd make disconnect() methods be sure everything they submitted > has been completed. > > (One requirement for disconnect methods has always been that > the urbs must have completed; that hasn't changed.)
Hi Dave, thanks for your answer. Why this last requirement? Doesn't it make "fire and forget" style urb submission awkward? Duncan. ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
