From: Johan Hovold <johan@kernel.org>
To: Karoly Pados <pados@pados.hu>
Cc: Johan Hovold <johan@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-usb@vger.kernel.org
Subject: USB: serial: cp210x: add Silicon Labs IDs for Windows Update
Date: Mon, 18 Jun 2018 09:46:15 +0200 [thread overview]
Message-ID: <20180618074615.GI32411@localhost> (raw)
On Mon, Jun 18, 2018 at 07:26:24AM +0000, Karoly Pados wrote:
> The way this works is that the chips still come with the standard
> SiLabs IDs. When the chip is integrated into an end-user product, the
> product manufacturer has the choice to reprogram the IDs. If they are
> left on the factory standard setting, the user will have to install
> drivers manually (go to SiLabs website, search, download, install by
> hand). Alternatively, the product manufacturer can reprogram the IDs
> to the "new" ones for Windows Update before shipping it to the
> customer, in which case Windows will automatically find, download, and
> install the drivers when plugged in the first time.
>
> More (official) info here: https://www.silabs.com/community/interface/knowledge-base.entry.html/2016/12/30/downloading_cp210xd-ek07
Thanks for the info.
> About the cutoff line: Sorry about that, now I know (first kernel
> patch for me). It seems you prefer to just adjust the commit message
> for now, otherwise let me know if you'd like me to resubmit.
Yeah, no worries. I've applied the patch for 4.17-rc with a stable tag
now.
Thanks,
Johan
---
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next reply other threads:[~2018-06-18 7:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-18 7:46 Johan Hovold [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-06-18 7:26 USB: serial: cp210x: add Silicon Labs IDs for Windows Update Karoly Pados
2018-06-18 7:10 Johan Hovold
2018-06-09 11:26 Karoly Pados
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=20180618074615.GI32411@localhost \
--to=johan@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-usb@vger.kernel.org \
--cc=pados@pados.hu \
/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;
as well as URLs for NNTP newsgroup(s).