David: It's not clear how the gadget API handles the data and status stages of a control transfer. The impression I have is that the queued requests are bi-directional; the gadget controller reads the request buffer if it gets an IN packet and writes the request buffer if it gets an OUT packet. But what happens for the status stage?
In zero.c, status requests are queued for control transfers involving no data. For IN control transfers (like GET INTERFACE or GET CONFIGURATION) the data request is queued but no status. What does the controller do in response to the status packet? There aren't any examples of OUT control transfers, but my guess is that the gadget driver must queue both a data request and a status request. Is that right? Alan Stern ------------------------------------------------------- This SF.net email is sponsored by: VM Ware With VMware you can run multiple operating systems on a single machine. WITHOUT REBOOTING! Mix Linux / Windows / Novell virtual machines at the same time. Free trial click here:http://www.vmware.com/wl/offer/358/0 _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
