> > Currently I've made a preliminary firmware for implementing the > > CDC-ACM interface, however as Pavel kindly pointed out for me, > > currently only 64Kbyte/sec is achieveable with this driver. I've read > > the archives and from the discussions, I suspect that this is > > connected to the NO_FSBR flag.. > > > > Questions which popped out of my mind: > > 1. Is there some standard way to allow for >64Kbytes/sec using the > > 2.6.x CDC-ACM driver? (I mean without modification of the sources, but > > setting some #defines or such) I'd not mind a reasonably slower PCI > > bus.. > > I don't know. I've never heard about a 64 KB/s limitation > for CDC-ACM.
This conversation is worrisome, I work with a number of devices that are accessed through usbserial and ACM (e.g. wireless/cellular modems) that have data rates in the 1-2 Mbits/s range. There are devices coming out in the next few months that will be in the 3-6 Mbits/s range with 13 Mbits/s a year out. This discussion of possible underlying data rate limitations in the CDC-ACM implementation is worrisome. Does anyone have a precise answer for what the data rate limitations are of these two implementations (usbserial and ACM)? I've made a switch from embedded OS to Linux recently in order to take advantage of Linux's native USB support and am wondering whether this was the wrong move. I'd be interested in whatever people have to say about this. Greg ------------------------------------------------------- SF.Net email is Sponsored by the Better Software Conference & EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf _______________________________________________ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
