Hi, Alan Stern: > usb_disconnect does not disable the chip -- that happens after it returns. > The only way usb_disconnect interacts with the controller is through the > hcd_endpoint_disable routine. That in turn does a normal unlink (which > you say will not work) and then calls the HCD's endpoint_disable method, > which is supposed to block until all URBs for the endpoint have completed. > Are you saying that the endpoint_disable method can force an uncompleted > unlink to complete? > usb_disconnect() ends up calling finish_unlink() with the pointer to the OHCI chip internals NULL, which is a valid way of saying "cleanup the damn list without looking at the OHCI state".
--
Matthias Urlichs | {M:U} IT Design @ m-u-it.de | [EMAIL PROTECTED]
Disclaimer: The quote was selected randomly. Really. | http://smurf.noris.de
- -
Message from Our Sponsor on ttyTV at 13:58 ...
signature.asc
Description: Digital signature
