Apologies if this ought to have gone to the USB maintainer (but his
auto-reply implies not).
I'm particularly interested in drivers/usb/core/config.c
which appears to enforce the USB specification by refusing to allow a
low speed CDC ACM. (Comment "Some buggy low-speed devices ...", at
about line
> From: "Felipe Balbi"
> > I'm particularly interested in drivers/usb/core/config.c
> > which appears to enforce the USB specification by refusing to allow a
> > low speed CDC ACM. (Comment "Some buggy low-speed devices ...", at
> > about line 300.)
> >
> > However, such devices exist and some ar
> From: "Greg KH"
> On Tue, Feb 07, 2017 at 05:51:05PM +0100, John Skelton wrote:
> > Apologies if this ought to have gone to the USB maintainer (but his
> > auto-reply implies not).
>
> This is the correct place.
Thanks.
> > I'm particularly inte
> From: "Greg KH"
> On Tue, Feb 07, 2017 at 06:56:20PM +0100, John Skelton wrote:
> > > From: "Felipe Balbi"
> > > > I'm particularly interested in drivers/usb/core/config.c
> > > > which appears to enforce the USB specification b
> From: "Greg KH"
> To: "John Skelton"
[snip]
> > > > It is code which is derived from V-USB
> > > > https://www.obdev.at/products/vusb/index.html
> > > > and is described at
> > > > http://www.recursion.jp/prose/avrcdc
> From: "Alan Stern"
> On Tue, 7 Feb 2017, John Skelton wrote:
> > > What happens after that? Does the cdc-acm driver refuse to bind? Any
> > > other types of error/warning messages?
> > > Along the lines of:
> > usb 2-1.2: >new low-speed USB de
