David: This probably resembles a question I asked before, but I'll ask it again just for kicks.
The USB Mass Storage Class CBI Transport Specification includes this paragraph: ------------------ 2.4.2.5 Data In: Host Requests Too Many Bytes If the host sends more IN PID than the device can satisy, then the device may NAK indefinitely (for more information, see section 2.3.2.4). The device should STALL (see section 2.4.3). ------------------ Granted that the indefinite NAK is most likely the way I'll go, nevertheless how would the Gadget API support the STALL alternative? Bear in mind that this STALL is _not_ supposed to happen if the host doesn't request too much IN data. Would queueing a 0-length bulk-in request and halting the endpoint within the completion routine do the trick? Or would the hardware simply ACK the transfer, meaning the host wouldn't see a STALL until the _next_ packet? Alan Stern ------------------------------------------------------- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01 _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
