From: Johan Hovold <johan@kernel.org>
To: Giles Roadnight <giles.roadnight@gmail.com>
Cc: linux-usb@vger.kernel.org
Subject: Re: Prolific Technology pl2303: unknown device type
Date: Mon, 20 Jun 2022 09:05:48 +0200 [thread overview]
Message-ID: <YrAcTDCnEiipWEM3@hovoldconsulting.com> (raw)
In-Reply-To: <CAA0uCUYnMjJxdsxjue3zD2-LZkJbg3imckTrV=4VakPMchdLWg@mail.gmail.com>
On Sat, Jun 18, 2022 at 07:42:43AM +0100, Giles Roadnight wrote:
> Hi
>
> I am trying to connect a Prolific pl2303 to my raspberry pi 4 running
> raspberry pi os 64 bit. When I look at dmesg I get the following
> output:
>
> [ 31.714397] cam-dummy-reg: disabling
> [ 44.046197] usb 1-1.1: USB disconnect, device number 3
> [ 47.254348] usb 1-1.1: new full-speed USB device number 4 using xhci_hcd
> [ 47.361386] usb 1-1.1: New USB device found, idVendor=067b,
> idProduct=23a3, bcdDevice= 6.05
> [ 47.361402] usb 1-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
> [ 47.361407] usb 1-1.1: Product: USB-Serial Controller
> [ 47.361412] usb 1-1.1: Manufacturer: Prolific Technology Inc.
> [ 47.361417] usb 1-1.1: SerialNumber: ALBAb115819
> [ 47.364081] pl2303 1-1.1:1.0: pl2303 converter detected
> [ 47.364106] pl2303 1-1.1:1.0: unknown device type, please report to
> linux-usb@vger.kernel.org
>
> so I followed the example and emailed this address!
>
> and with lsusb:
This has been fixed in mainline and backported to the relevant stable
trees (5.17.2, 5.16.19, 5.15.33) at the beginning of April.
You didn't mention which kernel you use, but updating to a more recent
one should fix this.
Johan
next prev parent reply other threads:[~2022-06-20 7:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAA0uCUZV0Jdc5HJnPg=Rqv06+UVYAudbx5qUNOatE9ZZsP6vsA@mail.gmail.com>
2022-06-18 6:42 ` Prolific Technology pl2303: unknown device type Giles Roadnight
2022-06-19 9:41 ` Giles Roadnight
2022-06-20 7:05 ` Johan Hovold [this message]
2022-06-20 7:10 ` Giles Roadnight
2022-06-20 7:19 ` 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=YrAcTDCnEiipWEM3@hovoldconsulting.com \
--to=johan@kernel.org \
--cc=giles.roadnight@gmail.com \
--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.