On Wednesday 16 January 2002 00:15, David Brownell wrote:
> > There are hundreds of drivers, and three hcds. Surely it would be better
> > to let the HCD do the relevant hoop jumping in these cases.
>
> They do. Apart from some massive (and it "really serioiusly"
> appears to me, intentional) confusion on Oliver's part, I don't
> see a problem.
No, the real simple solution here would be to state that an urb that has
been passed to a completion handler is referenced and must not be freed,
not even by the complition handler itself.
In the literal sense there are two references to that urb.
One is held by the complition handler/usbcore and the second is held by the
driver. The driver must retain a reference to an urb it has submitted, because
it needs a reference to unlink it.
Regards
Oliver
_______________________________________________
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
