All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Philipp Hortmann <philipp.g.hortmann@gmail.com>
Cc: Jonathan Kim <jonathankim@gctsemi.com>,
	Dean ahn <deanahn@gctsemi.com>, Won Kang <wonkang@gctsemi.com>,
	support@gctsemi.com, linux-kernel@vger.kernel.org,
	linux-staging@lists.linux.dev
Subject: Re: [RFC] staging: gdm724x: How to proceed with drivers gdmtty and gdmulte
Date: Wed, 24 Apr 2024 14:39:18 -0700	[thread overview]
Message-ID: <2024042433-reimburse-cork-8239@gregkh> (raw)
In-Reply-To: <78b521eb-4e89-4c01-8dfc-1fb990e6887d@gmail.com>

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

  reply	other threads:[~2024-04-24 21:39 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-22 17:55 [RFC] staging: ks7010: How to proceed with Spectec SDW-823 microSD driver Philipp Hortmann
2024-04-23 10:31 ` Wolfram Sang
2024-04-24 18:33   ` [RFC] staging: gdm724x: How to proceed with drivers gdmtty and gdmulte Philipp Hortmann
2024-04-24 21:39     ` Greg Kroah-Hartman [this message]
2024-09-28  6:41     ` [RFC] staging: gdm724x: Proposal to delete " Philipp Hortmann
2024-10-09  9:41       ` Greg Kroah-Hartman

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=2024042433-reimburse-cork-8239@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=deanahn@gctsemi.com \
    --cc=jonathankim@gctsemi.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-staging@lists.linux.dev \
    --cc=philipp.g.hortmann@gmail.com \
    --cc=support@gctsemi.com \
    --cc=wonkang@gctsemi.com \
    /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.