From: Greg KH <gregkh@linuxfoundation.org>
To: bugzilla-daemon@kernel.org
Cc: linux-usb@vger.kernel.org
Subject: Re: [Bug 221216] New: ezcap401 needs USB_QUIRK_NO_BOS to function on 10gbs usb speed
Date: Thu, 12 Mar 2026 18:30:31 +0100 [thread overview]
Message-ID: <2026031206-blissful-overlap-b484@gregkh> (raw)
In-Reply-To: <bug-221216-208809@https.bugzilla.kernel.org/>
On Thu, Mar 12, 2026 at 05:15:47PM +0000, bugzilla-daemon@kernel.org wrote:
> Hello, my new capture card works only in 5gbs usb speed, with deepseek's help I
> applied { USB_DEVICE(0x32ed, 0x0401), .driver_info = USB_QUIRK_NO_BOS }, to
> drivers/usb/core/quirks.c quirk and now it's working at full speed.
Can you send a patch that adds this entry to the kernel so that you get
this fixed properly?
thanks,
greg k-h
next prev parent reply other threads:[~2026-03-12 17:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-12 17:15 [Bug 221216] New: ezcap401 needs USB_QUIRK_NO_BOS to function on 10gbs usb speed bugzilla-daemon
2026-03-12 17:30 ` Greg KH [this message]
2026-03-12 17:30 ` [Bug 221216] " bugzilla-daemon
2026-03-12 17:35 ` bugzilla-daemon
2026-03-12 17:36 ` bugzilla-daemon
2026-03-12 17:52 ` Greg KH
2026-03-12 17:52 ` 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=2026031206-blissful-overlap-b484@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=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