> 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 device number 95 using ehci_hcd
> > usb 2-1.2: >device
Am Dienstag, den 07.02.2017, 19:01 +0100 schrieb John Skelton:
> I'm open to any suggestions. As I see it the above code is probably
> wrong
> in trying to use a low speed Bulk endpoint. The low performance of
> cheap
> Arduinos and digistump etc (with no hardware USB) is not going to
> allow
> a
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 device number 95 using ehci_hcd
> usb 2-1.2: >device descriptor read/64, error -32
On Tue, Feb 07, 2017 at 07:28:40PM +0100, John Skelton wrote:
> > 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 specificat
> 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/cdc-232.html
> > > >
> > > > If it worked with Linux it would be a handy way
> 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 by refusing to allow a
> > > > low speed CDC ACM. (Comment "Some bu
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 by refusing to allow a
> > > low speed CDC ACM. (Comment "Some buggy low-speed devices ...", a
> 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 interested in drivers/usb/core/config.c
> > which ap
> 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
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.
> I'm particularly interested in drivers/usb/core/config.c
> which appears to enforce the USB specification by
Hi,
John Skelton writes:
> 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 bugg
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
12 matches
Mail list logo
