hello,

        I have been looking through the sources of uchi.c, usb-ohci.c and
usb-uhci.c.
I was looking for error codes returned on URB completion and/or unlink.
At unlink, the uhci drivers call the completion handler and put the
error or ENOENT, beautifull ;-)
The ohci driver does not call the completion handler when unlinking the
urb, beautifull too ;-)
It can be helped with a small "if (urb->status) return;" statement in
the handler, but they should act the same, if only for uniformity.
There is another possible difference, but i am not really sure...
usb-ohci speaks of buffer under/overrun and returns -ECOMM,
usb-uhci/uhci speak of babble and generic buffer error and return both
EPIPE.
Are they talking about the same things here? I smeed like it to me, but
i don't know enough about the low level stuff to be sure...
Anyway, hope this helps...

        J.

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to