On Mon, 10 Jan 2005, CG wrote:
> Hi,
>
> Can you mind tell me if we have to send status after receiving CBW block
> data. I think that udc has never sent this block to the host. It's maybe
> why the host issues for a timeout and transfer again CBW block data.
For the CBW you included in your earlier email, what happens is this:
1. The gadget driver queues a bulk-in transfer (data phase).
2. The gadget driver tries to halt the bulk-in endpoint. It
on trying this in a loop until the udc says that it succeeded
(see the halt_bulk_in_endpoint() routine in file_storage.c).
3. The gadget driver queues a CSW (status phase) to the bulk-in
endpoint.
You probably never got beyond 2 because of the problems in the udc. If
you turn on debugging and verbose debugging (#define DEBUG and #define
VERBOSE near the beginning of the source file) you'll see all these things
happening in the dmesg log.
Alan Stern
-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
_______________________________________________
linux-usb-devel@lists.sourceforge.net
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
