On Sun, 27 Nov 2005, Steve Calfee wrote:
> >When a control request arrives on ep0 and the gadget has to do a lot of
> >processing before completing the data or status stages of the request,
> >there's a possibility that the host might time out and send another
> >request to ep0. If this happens,
Dave:
I may have asked this before; if so I've forgotten the answer.
When a control request arrives on ep0 and the gadget has to do a lot of
processing before completing the data or status stages of the request,
there's a possibility that the host might time out and send another
request to ep0.
[EMAIL PROTECTED] wrote:
Hello,
I'm about to use the gadget drivers on a 2.4 kernel in a PC/104 embedded
computer. For beginning, I have to write low-level drivers for Philips PDIUSBD12
chip that I access through parallel-port (see http://www.usbdeveloper.com).
Where may I find the "official" gadg
Hello,
I'm about to use the gadget drivers on a 2.4 kernel in a PC/104 embedded
computer. For beginning, I have to write low-level drivers for Philips PDIUSBD12
chip that I access through parallel-port (see http://www.usbdeveloper.com).
Where may I find the "official" gadget drivers, since I only
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
