From: bugzilla-daemon@kernel.org
To: linux-usb@vger.kernel.org
Subject: [Bug 220027] USB 3.2 capture cards using incorrect USB speed
Date: Sun, 15 Feb 2026 06:59:18 +0000 [thread overview]
Message-ID: <bug-220027-208809-VtSAS4UfLK@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 #15 from Greg Kroah-Hartman (greg@kroah.com) ---
On Sat, Feb 14, 2026 at 09:27:56PM +0000, bugzilla-daemon@kernel.org wrote:
> This has been solved by multiple patches including
>
> https://lore.kernel.org/linux-usb/20251207012059.7899-1-johannes.bruederl@gmail.com/
> (this thread) and
>
> https://lore.kernel.org/linux-usb/2026020536-bullseye-smugly-4361@gregkh/T/#mf7393976d02d49cbfdb9ff5c46f030dfc0f7a6c7
>
> So technically you can make a kernel yourself and it would work, but neither
> of
> these have been merged as I think there is confusion about how the cards
> work.
Yes, these have been merged, please use a newer kernel version please.
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
prev parent reply other threads:[~2026-02-15 6:59 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
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 [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-220027-208809-VtSAS4UfLK@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.