linux-usb.vger.kernel.org archive mirror
 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: Sat, 03 May 2025 15:59:10 +0000	[thread overview]
Message-ID: <bug-220027-208809-6ZPtiaqpi4@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 #11 from Michał Pecio (michal.pecio@gmail.com) ---
(In reply to Niko from comment #10)
> Here is the output of 'lsusb -d 0fd9:009b -v', Do you want me to boot into
> an unpatched kernel so I can do the same for the other PID (0x009c)?
No, the point was to run lsusb as root at 10G speed. As root, it will request
the BOS descriptor (bypassing the patched kernel code) so we could see if the
device has a temporary problem with BOS at that particular stage of
enumeration, or if it's completely broken and never responds to this request.

I think it may be completely broken, because I installed Wireshark on Windows
and it looks like my Windows 10 doesn't fetch BOS descriptors from SuperSpeed
devices at all (maybe it does from hubs, I haven't tried).

-- 
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-03 15:59 UTC|newest]

Thread overview: 13+ 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
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 [this message]
2025-05-04  0:27 ` 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-6ZPtiaqpi4@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;
as well as URLs for NNTP newsgroup(s).