From: Greg KH <gregkh@linuxfoundation.org>
To: Charles Yeh <charlesyeh522@gmail.com>
Cc: "Johan Hovold" <johan@kernel.org>,
linux-usb@vger.kernel.org,
"Yeh.Charles [葉榮鑫]" <charles-yeh@prolific.com.tw>
Subject: Re: [PATCH] USB: serial: pl2303: Add new PID to support PL256X (TYPE_MP)
Date: Fri, 5 Nov 2021 11:02:48 +0100 [thread overview]
Message-ID: <YYUBSO/Jj+99btPr@kroah.com> (raw)
In-Reply-To: <CAAZvQQ6q4Kg2iHkD4JefJ3r=pa9Gbz_y_5utgwSGQL_2HH7Ohg@mail.gmail.com>
On Mon, Nov 01, 2021 at 12:53:03PM +0800, Charles Yeh wrote:
> This issue can be closed.
>
> Sorry, it took so long to reply...
> Finally, our company(Prolific) decided to change the new chip from
> "Class FFh (Vendor Specific)" to "Class 02h (Communications and CDC Control)"
> In this way, the chip's default support can be backward compatible
> with the lower version of the Linux kernel (such as 3.X / 4.X,...)
But is the device really compliant with the CDC specification? If so,
wonderful, but if not, then:
> If there are customers who need RTS/CTS and other flow control in the future.
> We(Prolific) will provide patch file to support
That is very odd, we can take such a patch now in the kernel source tree
so that you will not have to deal with this for the thousands of
different companies wanting this. Please submit the needed patch here
and we will be glad to review it.
When a person has to run a patched kernel, they loose the support of the
vendor they are getting their kernel from, so you would require anyone
who runs your changed driver to invalidate their vendor support
contract. Not something that I am sure anyone would really want to do
"just" for a usb to serial device.
thanks,
greg k-h
prev parent reply other threads:[~2021-11-05 10:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-22 12:09 [PATCH] USB: serial: pl2303: Add new PID to support PL256X (TYPE_MP) Charles Yeh
2021-07-22 5:16 ` Charles Yeh
2021-07-22 7:40 ` Johan Hovold
[not found] ` <CAAZvQQ6Kr0vbDAnKYum9EaCVxc9Ps69vBV+sg2mov06tB4KqNg@mail.gmail.com>
2021-07-22 5:50 ` Greg KH
2021-08-04 10:54 ` Johan Hovold
2021-11-01 4:53 ` Charles Yeh
2021-11-05 10:02 ` Greg KH [this message]
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=YYUBSO/Jj+99btPr@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=charles-yeh@prolific.com.tw \
--cc=charlesyeh522@gmail.com \
--cc=johan@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 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.