From: Johan Hovold <johan@kernel.org>
To: Giles Roadnight <giles.roadnight@gmail.com>
Cc: glance@acc.umu.se, linux-usb@vger.kernel.org
Subject: Re: pl2303 converter detected, unknown device type
Date: Mon, 20 Jun 2022 09:15:27 +0200 [thread overview]
Message-ID: <YrAej8OuOC2lvmb6@hovoldconsulting.com> (raw)
In-Reply-To: <CAA0uCUZSVmAijR8VkkCbW4nEVo=v__U_sjB0UVSbNQsgPKTxrA@mail.gmail.com>
On Sun, Jun 19, 2022 at 10:10:37AM +0100, Giles Roadnight wrote:
> Was there ever any resolution to this? I am having the same issue and
> have tried multiple combinations of different Raspberry pi os and pi
> and get the same issue.
>
> Johan - did you add support for this model? If so how to update to the
> latest version so that I can use this usb device?
You appear to have a different device than the one Anton reported (e.g.
PL2303GS instead of PL2303GC), but the fix is similar and was
merged in March as I just mentioned in my other mail.
> (forgive the basic questions, I am not very experienced with linux so
> don't know what bit I need to update to get the latest usb drivers -
> or whatever it is you updated)
Just make sure you update to a recent mainline or stable kernel (e.g.
5.17.2, 5.16.19, 5.15.33 or newer) or wait until your distro kernel
catches up.
The commit you need is
5b6ab28d0678 ("USB: serial: pl2303: fix GS type detection")
if you want to report it to the distro.
Johan
next prev parent reply other threads:[~2022-06-20 7:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-19 9:10 pl2303 converter detected, unknown device type Giles Roadnight
2022-06-20 7:15 ` Johan Hovold [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-11-23 7:16 Anton Lundin
2021-11-23 8:13 ` Johan Hovold
2021-11-23 8:34 ` Anton Lundin
2021-11-23 8:59 ` Johan Hovold
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=YrAej8OuOC2lvmb6@hovoldconsulting.com \
--to=johan@kernel.org \
--cc=giles.roadnight@gmail.com \
--cc=glance@acc.umu.se \
--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;
as well as URLs for NNTP newsgroup(s).