All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@kernel.org
To: linux-usb@vger.kernel.org
Subject: [Bug 220331] FTDI serial IO - unknown device type: 0x8312
Date: Wed, 27 Aug 2025 08:37:15 +0000	[thread overview]
Message-ID: <bug-220331-208809-s8xTHXLd7p@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-220331-208809@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=220331

--- Comment #4 from Johan Hovold (johan@kernel.org) ---
On Thu, Jul 10, 2025 at 09:11:14AM +0000, bugzilla-daemon@kernel.org wrote:
> https://bugzilla.kernel.org/show_bug.cgi?id=220331

> Issue with a newer hardware with USB DisplayLink adapter, syslog throws
> following error about unrecognized device type 0x8312:
> 
> > [    4.447826] usb 1-8.2.1: New USB device found, idVendor=17e9,
> > idProduct=ff00, bbcdDevice=83.12
> > [    4.447833] usb 1-8.2.1: New USB device strings: Mfr=1, Product=2,
> > SerialNumber
> > =3
> > [    4.447835] usb 1-8.2.1: Product: PM1000
> > [    4.447836] usb 1-8.2.1: Manufacturer: DisplayLink
> > [    4.447837] usb 1-8.2.1: SerialNumber: 9638293100007141

This does not look like an FTDI device and as far as I can see ftdi_sio
driver should not even try to bind to it currently as the VID/PID is not
in the driver's match table.

> > [    4.479297] usbcore: registered new interface driver ftdi_sio
> > [    4.479363] usbserial: USB Serial support registered for FTDI USB Serial
> > Device
> > [    4.480786] ftdi_sio 1-8.2.1:1.0: FTDI USB Serial Device converter
> > detected
> > [    4.480848] ftdi_sio ttyUSB0: unknown device type: 0x8312
> > [    4.480923] ftdi_sio 1-8.2.1:1.1: FTDI USB Serial Device converter
> > detected
> > [    4.480957] ftdi_sio ttyUSB1: unknown device type: 0x8312
> > [    4.486014] ftdi_sio ttyUSB0: unknown device type: 0x8312
> > [    4.486049] ftdi_sio ttyUSB1: unknown device type: 0x8312

Please post the output of "lsusb -v" for this device.

Johan

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

      parent reply	other threads:[~2025-08-27  8:37 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-10  9:11 [Bug 220331] New: FTDI serial IO - unknown device type: 0x8312 bugzilla-daemon
2025-07-11  6:00 ` [Bug 220331] " bugzilla-daemon
2025-07-21 14:58 ` bugzilla-daemon
2025-07-21 15:37   ` Greg KH
2025-07-21 15:37 ` bugzilla-daemon
2025-08-27  8:37 ` [Bug 220331] New: " Johan Hovold
2025-08-27  8:37 ` bugzilla-daemon [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=bug-220331-208809-s8xTHXLd7p@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@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.