Hi.
I'm currently working on a HC for the CRIS architecture and I'm
wondering if there is a summary of the possible codes for the URB status?
When does the USB Core set it and when is the HC supposed to change it?
I've seen that some drivers don't resubmit the URB if it finishes with
the -ENOENT.
How can the HC see de difference between a usb_unlink_urb() and
usb_kill_urb() when they both issues the same function call
urb_dequeue() down to the HC?
I've seen that the USB Core presets the URB status to -ENOENT before
calling urb_dequeue() in the HC for some cases but also -ESHUTDOWN.
Difference?
How does most device-drivers handle this?
When running test 11 & 12 from usbtest.c both unlink and kill uses
urb_dequeue() and can have the URB_ASYNC_UNLINK flag sat. Can a
usb_kill_urb() really be asynchronous?
Thanks in advance
Konrad Erikson
for Axis Communication AB
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
[email protected]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
