From: Greg KH <gregkh@linuxfoundation.org>
To: Josh Cabarrus <joshcabarrus@gmail.com>
Cc: linux-usb@vger.kernel.org, laurent.pinchart@ideasonboard.com,
balbi@kernel.org
Subject: Re: g_webcam UVC gadget causes USB\DEVICE_DESCRIPTOR_FAILURE on Windows 11
Date: Wed, 28 May 2025 06:34:01 +0200 [thread overview]
Message-ID: <2025052821-certified-remission-05fd@gregkh> (raw)
In-Reply-To: <CAD=osaSH51vGF_zq2ArWY-6jCuG0LfMO5guSE9mgGpc-YPWOtw@mail.gmail.com>
On Tue, May 27, 2025 at 08:48:20PM -0600, Josh Cabarrus wrote:
> Bug Report: g_webcam UVC gadget incompatible with Windows 11 USB
> descriptor validation
Has this ever worked in the past? If so, what kernel versions did work,
and can you use git bisect to track down the offending commits?
If it has never worked, any patches to change the code to make it work
would be appreciated.
> Could the maintainers investigate updating g_webcam's USB descriptors
> to meet Windows 11's stricter validation requirements? The fact that
> g_serial works but g_webcam fails suggests this is a
> descriptor-specific issue rather than hardware or driver framework
> problem.
g_serial is trivial compared to g_webcam, so this is not really a fair
comparison. What changed in windows 11 descriptor requirements? Do you
have a pointer to the relevant documentation for where it is explained
what has changed?
And what exact descriptors are failing here?
> I can provide:
>
> USB protocol analyzer captures
> Testing with different Windows versions
Did windows 10 work?
> Comparison with working UVC implementations
Great, that might be the simplest, what descriptors work, and what do
not?
thanks,
greg k-h
prev parent reply other threads:[~2025-05-28 4:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-28 2:48 g_webcam UVC gadget causes USB\DEVICE_DESCRIPTOR_FAILURE on Windows 11 Josh Cabarrus
2025-05-28 4:34 ` 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=2025052821-certified-remission-05fd@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=balbi@kernel.org \
--cc=joshcabarrus@gmail.com \
--cc=laurent.pinchart@ideasonboard.com \
--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