On Wed, 25 Jan 2012, Nikolai Zhubr wrote: > Hello Alan, > 24.01.2012 22:30, Alan Stern: > > On Tue, 24 Jan 2012, Nikolai Zhubr wrote: > > > >> Hello Alan, > >> 24.01.2012 19:45, Alan Stern: > >> [trim] > >>> Does this mean that the hardware has only one FIFO? Or only one for > >>> each direction? That's a pretty limited design. > > Just to be precise. I've checked this again. Unfortunately in my > specific device dedicated FIFOs are not present. In other words, only > one Tx FIFO is available indeed. The driver does understand this, but > see yet another comment extracted from the code regarding the mismatch > error (follows below). I'd note that the actions suggested in its second > part are not implemented anywhere, the handler just dumps debug info and > exits. The "IN Token Queue Registers" always show zeroes. And this is > put into real products! Makes me wonder. > > Yes, probably the design is so limited that it maybe isn't worth fixing > in the driver, but what is frustrating is that it _almost_ works... Is the same Tx FIFO used for bulk endpoints and ep0? If not, then you could restrict the driver to support only one bulk-IN endpoint whenever dedicated FIFOs aren't present. Alan Stern -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
