On Sat, Dec 24, 2022 at 07:53:54AM +0100, Greg KH wrote:
> On Fri, Dec 23, 2022 at 11:51:48PM +0000, dima.pasechnik@cs.ox.ac.uk wrote:
> > 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.
> 
> I do not understand here, are you asking me to talk to someone?  If so,
> great, who?  If not, who are you asking?
> 
> > Can PID be bumped up by a firmware update?
> 
> Depends on how the hardware was designed.  Most can, some can not.  Is
> the hardware design and firmware source available anywhere?
As far I know, firmware comes from
https://tech.microbit.org/software/runtime/

As to why these V1 and V2 happened to get the same product ID, perhaps
my colleague Mike, in CC, who teaches a course using this board,  knows more.

Cheers
Dima