public inbox for linux-usb@vger.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@kernel.org
To: linux-usb@vger.kernel.org
Subject: [Bug 220027] USB 3.2 capture cards using incorrect USB speed
Date: Fri, 02 May 2025 09:41:09 +0000	[thread overview]
Message-ID: <bug-220027-208809-6ypDFQj1lA@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-220027-208809@https.bugzilla.kernel.org/>

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

--- Comment #7 from Michał Pecio (michal.pecio@gmail.com) ---
Created attachment 308070
  --> https://bugzilla.kernel.org/attachment.cgi?id=308070&action=edit
don't fetch BOS descriptors from devices

Maybe something like this patch, then?

Your device seems to hang when asked for this descriptor, so don't ask it and
see what happens. I tried it on my own 5Gbps UVC device and it still works,
though many other things break without BOS and hence the patch checks for
vendor ID. You will need to edit it with the ID of your device. The patch also
prints IDs of new devices to a) confirm that the earlier device descriptor
request was successful and b) help with adjusting the patch if 10Gbps vendor ID
is different from 5Gbps vendor ID.

It should now look like this:
[89023.940009] usb 19-2.3: new SuperSpeed USB device number 8 using xhci_hcd
[89023.954100] usb 19-2.3: new device idVendor ac8 idProduct 3420
[89023.954115] usb 19-2.3: too lazy to get BOS descriptor or descriptor too
short

-- 
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-05-02  9:41 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-17 18:26 [Bug 220027] New: USB 3.2 capture cards using incorrect USB speed bugzilla-daemon
2025-04-18  1:07 ` [Bug 220027] " bugzilla-daemon
2025-04-26  8:39 ` bugzilla-daemon
2025-04-26 16:15 ` bugzilla-daemon
2025-04-27 23:27 ` bugzilla-daemon
2025-04-30  6:35 ` bugzilla-daemon
2025-04-30 19:54 ` bugzilla-daemon
2025-05-02  9:41 ` bugzilla-daemon [this message]
2025-05-02 15:19 ` bugzilla-daemon
2025-05-02 20:36 ` bugzilla-daemon
2025-05-03 15:31 ` bugzilla-daemon
2025-05-03 15:59 ` bugzilla-daemon
2025-05-04  0:27 ` bugzilla-daemon
2026-02-12 21:59 ` bugzilla-daemon
2026-02-14 21:27 ` bugzilla-daemon
2026-02-15  6:59   ` Greg KH
2026-02-15  6:59 ` bugzilla-daemon

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-220027-208809-6ypDFQj1lA@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox