From: Greg KH <gregkh@linuxfoundation.org>
To: sharms <sharms@snowfoundry.com>
Cc: dev@a1rm4x.com, linux-usb@vger.kernel.org,
linux-kernel@vger.kernel.org, limiao@kylinos.cn,
oneukum@suse.com, huanglei@kylinos.cn, lijiayi@kylinos.cn,
johannes.bruederl@gmail.com
Subject: Re: [PATCH] usb: add QUIRK_NO_BOS for several devices
Date: Thu, 5 Feb 2026 18:33:23 +0100 [thread overview]
Message-ID: <2026020536-bullseye-smugly-4361@gregkh> (raw)
In-Reply-To: <20260205172432.1007632-1-sharms@snowfoundry.com>
On Thu, Feb 05, 2026 at 10:24:32AM -0700, sharms wrote:
> From: Steve Harms <sharms@snowfoundry.com>
>
> On Thu, Feb 05, 2026 at 07:51:17AM +0100, Greg KH wrote:
> > Ok, it looks like there is a very broken USB controller chip out there
> > in all of these devices.
>
> Hey Greg,
>
> I think this references the same issues as in
> https://lore.kernel.org/linux-usb/2025122837-creamlike-motivator-8dcb@gregkh/
Yes.
> There are a few of us who need 10G support for video capture with
> these devices.
Understood, and I guess they are all using the same chip in the device?
I have the one listed at the link above for testing, but it would be
really good if someone could figure out why Windows doesn't have this
problem and only Linux does...
thanks,
greg k-h
prev parent reply other threads:[~2026-02-05 17:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-04 3:29 [PATCH] usb: add QUIRK_NO_BOS for several devices A1RM4X
2026-02-04 5:15 ` Greg KH
2026-02-04 14:25 ` A1RM4X
2026-02-04 14:36 ` Greg KH
2026-02-04 14:37 ` Greg KH
2026-02-04 19:51 ` A1RM4X
2026-02-05 6:51 ` Greg KH
2026-02-05 17:24 ` sharms
2026-02-05 17:33 ` Greg KH [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=2026020536-bullseye-smugly-4361@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=dev@a1rm4x.com \
--cc=huanglei@kylinos.cn \
--cc=johannes.bruederl@gmail.com \
--cc=lijiayi@kylinos.cn \
--cc=limiao@kylinos.cn \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=oneukum@suse.com \
--cc=sharms@snowfoundry.com \
/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