mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Steven Turgetto <Steven.Turgetto@clinicomp.com>,
	Linux USB <linux-usb@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Cc: Donny Callego <Donny.Callego@clinicomp.com>,
	Jeremy Simmons <jeremy.simmons@clinicomp.com>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: Re: Update needed for pl2303 module (resending in plain text)
Date: Sat, 16 Sep 2023 07:33:18 +0700	[thread overview]
Message-ID: <ZQT3zmTSg7hfY-uU@debian.me> (raw)
In-Reply-To: <CO6PR11MB5572CB5C140AD3B9C67DEE0CEAF6A@CO6PR11MB5572.namprd11.prod.outlook.com>

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

On Fri, Sep 15, 2023 at 11:47:23PM +0000, Steven Turgetto wrote:
> Hello,
> 
> CliniComp has a device which reports bcdUSB=0x200 and bcdDevice=0x400. This configuration is necessary for our product to support some legacy hardware. 
> 
> In the pl2303 driver included with the RedHat Enterprise Linux kernel 4.18.0-477.10.1.el8_8.x86_64 , we added the following two lines to pl2303_detect_type function at line 449.
>                 case 0x400:
>                         return TYPE_HX;
> 
> Would you please let me know if you are able to support our device in the pl2303 driver?

Can you send above suggestion as formal patch (see
Documentation/process/submitting-patches.rst for how to submit patches)?

And also, shouldn't you contact RedHat support instead since you run
EL kernel?

Thanks.

-- 
An old man doll... just what I always wanted! - Clara

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

           reply	other threads:[~2023-09-16  0:35 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <CO6PR11MB5572CB5C140AD3B9C67DEE0CEAF6A@CO6PR11MB5572.namprd11.prod.outlook.com>]

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=ZQT3zmTSg7hfY-uU@debian.me \
    --to=bagasdotme@gmail.com \
    --cc=Donny.Callego@clinicomp.com \
    --cc=Steven.Turgetto@clinicomp.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=jeremy.simmons@clinicomp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®