[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <2024042433-reimburse-cork-8239@gregkh>
Date: Wed, 24 Apr 2024 14:39:18 -0700
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: Philipp Hortmann <philipp.g.hortmann@...il.com>
Cc: Jonathan Kim <jonathankim@...semi.com>, Dean ahn <deanahn@...semi.com>,
Won Kang <wonkang@...semi.com>, support@...semi.com,
linux-kernel@...r.kernel.org, linux-staging@...ts.linux.dev
Subject: Re: [RFC] staging: gdm724x: How to proceed with drivers gdmtty and
gdmulte
On Wed, Apr 24, 2024 at 08:33:25PM +0200, Philipp Hortmann wrote:
> Dear Sirs,
>
> Won Kang contributed a driver gdm724x to the Linux kernel staging subsystem
> in 2013. Have you done any tests with this hardware in the years up to
> today?
>
> struct usb_device_id lists the following devices the driver can work with:
> PID_GDM7240 0x8000
> PID_GDM7243 0x9000
>
> but on http://www.linux-usb.org/usb.ids I can only find:
> 0x1076 GCT Semiconductor, Inc.
> 0x0031 Bluetooth Device
> 0x0032 Bluetooth Device
> 0x8002 LU150 LTE Modem [Yota LU150]
Note, not all USB devices (I would guess only a fraction) are listed in
the usb.ids file because USB devices are self-described (i.e. the
strings are in the device itself). So don't go by the presence or not
of a device in this file to determine if it is "real" or not.
thanks,
greg k-h
Powered by blists - more mailing lists