From: "Matyáš Kroupa" <kroupa.matyas@gmail.com>
To: linux-usb@vger.kernel.org
Subject: Another PL2303
Date: Sun, 6 Mar 2022 17:52:58 +0100 [thread overview]
Message-ID: <165de6a0-43e9-092c-2916-66b115c7fbf4@gmail.com> (raw)
Hi,
I recently bought a serial console adapter with PL2303. After a quick
search I discovered that there have been problems with different
versions of this chip so I include some info about mine.
Thanks in advance
Matyáš
dmesg:
[172076.820388] usb 3-2.2: new full-speed USB device number 11 using
xhci_hcd
[172076.960358] usb 3-2.2: New USB device found, idVendor=067b,
idProduct=23f3, bcdDevice= 6.05
[172076.960372] usb 3-2.2: New USB device strings: Mfr=1, Product=2,
SerialNumber=3
[172076.960377] usb 3-2.2: Product: USB-Serial Controller
[172076.960381] usb 3-2.2: Manufacturer: Prolific Technology Inc.
[172076.960384] usb 3-2.2: SerialNumber: CCBLj19B616
[172077.038242] usbcore: registered new interface driver pl2303
[172077.038251] usbserial: USB Serial support registered for pl2303
[172077.038269] pl2303 3-2.2:1.0: pl2303 converter detected
[172077.038273] pl2303 3-2.2:1.0: unknown device type, please report to
linux-usb@vger.kernel.org
lsusb:
Bus 003 Device 011: ID 067b:23f3 Prolific Technology, Inc. USB-Serial
Controller
Couldn't open device, some information will be missing
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 0
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
idVendor 0x067b Prolific Technology, Inc.
idProduct 0x23f3
bcdDevice 6.05
iManufacturer 1 Prolific Technology Inc.
iProduct 2 USB-Serial Controller
iSerial 3 CCBLj19B616
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 0x0027
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0xa0
(Bus Powered)
Remote Wakeup
MaxPower 100mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 3
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 0
bInterfaceProtocol 0
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x000a 1x 10 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x02 EP 2 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x83 EP 3 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 0
next reply other threads:[~2022-03-06 16:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-06 16:52 Matyáš Kroupa [this message]
2022-03-07 14:29 ` Another PL2303 Johan Hovold
2022-03-07 14:38 ` Matyáš Kroupa
2022-03-07 14:40 ` 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=165de6a0-43e9-092c-2916-66b115c7fbf4@gmail.com \
--to=kroupa.matyas@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.