linux-kernel - Re: [PATCH] USB: serial: ftdi_sio: add device ID for U-Blox EVK-M101

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <aQMykuOFuwi0OTdi@hovoldconsulting.com>
Date: Thu, 30 Oct 2025 10:40:34 +0100
From: Johan Hovold <johan@...nel.org>
To: Oleksandr Suvorov <cryosay@...il.com>
Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
	linux-usb@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] USB: serial: ftdi_sio: add device ID for U-Blox EVK-M101

On Thu, Oct 30, 2025 at 09:39:36AM +0200, Oleksandr Suvorov wrote:
> On Wed, Oct 15 2025 at 16:36 Johan Hovold <johan@...nel.org> wrote:

> > > has a USB Type-C port that presents itself as a USB device
> > > (1546:0506) [1] with four attached FTDI serial ports, connected to:
> > > - EVK-M101 current sensors
> > > - EVK-M101 I2C
> > > - EVK-M101 UART
> > > - EVK-M101 port D
> > >
> > > This commit registers U-Blox's VID/PID of this device so that FTDI SIO driver
> > > successfully registers these 4 serial ports.
> >
> > Are you sure you should not just register the UART port? Some FTDI chips
> > support I2C but you'd need a different driver for that.
> 
> Thanks for pointing this out, looks like I should add a custom probe()
> for this device.
> Preparing v2.

Actually, you can just use USB_DEVICE_INTERFACE_NUMBER() in the match
table, no need for a custom probe function.

> > > Datasheet: https://content.u-blox.com/sites/default/files/documents/EVK-M10_UserGuide_UBX-21003949.pdf
> >
> > The user guide also says "Do not use this COM port" for all ports but
> > the UART port.
> 
> Yes, you're right, thanks. It's just not that easy hacking the kernel
> while defending from russian invaders :)

I can only imagine.

Johan