Hello Julian,
> I've based my Superh UDC driver on the pxa2xx_udc. The ep0 handling is
> different (simpler) but the other endpoints are very similar. I didn't
> really look at the net2280 code as it seemed much too complex for my
> device, so I hadn't realised that it does queue management i
I've based my Superh UDC driver on the pxa2xx_udc. The ep0 handling is
different (simpler) but the other endpoints are very similar. I didn't
really look at the net2280 code as it seemed much too complex for my
device, so I hadn't realised that it does queue management in hardware.
It seems
Miroslaw KLABA wrote:
Hello,
I wanted to know if there are any controller driver already written for Gadget
API, other than the netchip 2280 one?
Yes, like the pxa2xx_udc ... the net2280 isn't the simplest example,
I'd agree. Not all controller hardware supports transfer queues in
hardware; but t
Hello Julian,
> I would have thought that your device does have at least a one byte
> transmit/recieve buffer per end point. So can't you just write the
> driver as if it had a 1 byte FIFO?
In fact, it has FIFO buffers for each endpoint. But I think I've understood now how
the queue works in
On Fri, Oct 03, 2003 at 09:56:56AM +0200, Miroslaw KLABA wrote:
> I wanted to know if there are any controller driver already written
> for Gadget API, other than the netchip 2280 one?
David's bk tree contains a PXA2xx driver as well.
Robert
--
Dipl.-Ing. Robert Schwebel | http://www.pengutron
I'm writing a controller driver for the UDC in some Renesas SuperH
devices. It is more or less working now but does need more testing and
debugging. My device is more basic in some respects than the existing
gadget UDC drivers but it does still have on-chip FIFOs.
I would have thought that yo
Hello,
I wanted to know if there are any controller driver already written for Gadget
API, other than the netchip 2280 one?
I've got problems with the usb_ep_queue function. The chip, I want to write the
code for (Philips D12), has no FIFO inside, so either I have to make the
usb_ep_queue not real
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
