From: bugzilla-daemon@kernel.org
To: linux-usb@vger.kernel.org
Subject: [Bug 220027] USB 3.2 capture cards using incorrect USB speed
Date: Wed, 30 Apr 2025 06:35:59 +0000 [thread overview]
Message-ID: <bug-220027-208809-iqsjuuBYDN@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 #5 from Michał Pecio (michal.pecio@gmail.com) ---
Looks like a problem with those capture devices, then. Maybe they all use the
same chip? One name I have seen somewhere is Realtek RTD2801VPF.
It could be what Mathias Nyman suggested in the other bug: the device expects
some particular order of descriptor requests (as issued by Windows) and doesn't
know what to do when Linux does similar things in other order. It would be a
little weird that such a bug only occurs at 10G speed, but hardware can be all
sorts of buggy...
To test this theory it would be necessary to patch the kernel and observe what
happens. Can you build the kernel from source, are you familiar with C
programming by any chance?
Another possible approach is to sniff the USB bus with Wireshark on Windows and
on Linux and compare. Disclaimer: I have never really used Wireshark on Windows
before, so IDK how usable it is, and any changes to Linux behavior would still
require kernel patches of course.
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2025-04-30 6:35 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 [this message]
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
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-iqsjuuBYDN@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