All of lore.kernel.org
 help / color / mirror / Atom feed
From: dima.pasechnik@cs.ox.ac.uk
To: Greg KH <gregkh@linuxfoundation.org>
Cc: Alan Stern <stern@rowland.harvard.edu>, linux-usb@vger.kernel.org
Subject: Re: usb 1-3: Product: BBC micro:bit CMSIS-DAP not recognised
Date: Fri, 23 Dec 2022 23:51:48 +0000	[thread overview]
Message-ID: <Y6Y/FB1IS6BrKsCW@hilbert> (raw)
In-Reply-To: <Y6XAMmx7LjDn1J6R@kroah.com>

[-- Attachment #1: Type: text/plain, Size: 1135 bytes --]

On Fri, Dec 23, 2022 at 03:50:26PM +0100, Greg KH wrote:
> On Tue, Dec 20, 2022 at 01:08:59PM +0000, dima.pasechnik@cs.ox.ac.uk wrote:
> > On Mon, Dec 19, 2022 at 06:36:47PM -0500, Alan Stern wrote:
> > > 
> > > It might help if you post the output of "lsusb -v" for this device.
> > Please see attached; I also attached the output for an older version of
> > this board (V1). The one we talk about is V2. Both versions have the
> > same VID, and, weirdly, the same PID (internally they aren't binary
> > compatible, even)
> 
> That's horrible, someone should talk to the vendor here and get them to
> at least bump the device id.

The vendor is ARM (https://www.arm.com/) - I guess Linux Foundation is a good "someone"
to talk to the vendor in this case.

Can PID be bumped up by a firmware update?


> 
> Anyway, I don't see a "serial" device here, just use the cdc-acm driver
> and all should be ok, right?  Is there any missing functionality that
> you feel is required that only the usb-serial api can provide?
Not at this point, no. Perhaps I'll resurrect this if I find something
out.

Best,
Dmitrii

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2022-12-23 23:51 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-19 12:57 usb 1-3: Product: BBC micro:bit CMSIS-DAP not recognised dima.pasechnik
2022-12-19 15:00 ` Greg KH
2022-12-19 16:29   ` dima.pasechnik
2022-12-19 18:10     ` dima.pasechnik
2022-12-19 18:25       ` Greg KH
2022-12-19 22:20         ` dima.pasechnik
2022-12-19 23:36           ` Alan Stern
2022-12-20 13:08             ` dima.pasechnik
2022-12-23 14:50               ` Greg KH
2022-12-23 23:51                 ` dima.pasechnik [this message]
2022-12-24  6:53                   ` Greg KH
2022-12-25 11:08                     ` dima.pasechnik
2022-12-25 18:52                       ` Mike Spivey
2022-12-20  6:57           ` Greg KH
2022-12-20 14:50             ` dima.pasechnik
2022-12-20 19:57               ` Alan Stern
2022-12-22 10:32                 ` Dima Pasechnik
2022-12-22 21:24                   ` Alan Stern
2022-12-23 12:58                     ` Dmitrii Pasechnik
2022-12-23 14:52                       ` Alan Stern
2022-12-23 23:41                         ` Dmitrii Pasechnik
2022-12-24 16:00                           ` Alan Stern
2022-12-31 19:49                             ` Jó Ágila Bitsch

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Y6Y/FB1IS6BrKsCW@hilbert \
    --to=dima.pasechnik@cs.ox.ac.uk \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=stern@rowland.harvard.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.