From: Greg KH <greg@kroah.com>
To: "Vrastil, Michal" <michal.vrastil@hidglobal.com>
Cc: "linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>
Subject: Re: [PATCH] usb: gadget: composite: fix OS descriptors w_value logic
Date: Tue, 3 Sep 2024 13:23:30 +0200 [thread overview]
Message-ID: <2024090305-harmonica-strained-ed09@gregkh> (raw)
In-Reply-To: <AS8PR05MB848522189AE458978C5F231490932@AS8PR05MB8485.eurprd05.prod.outlook.com>
On Tue, Sep 03, 2024 at 11:14:39AM +0000, Vrastil, Michal wrote:
> >From 118f8c8b72d633c0daa65e564e48cbf4964977ab Mon Sep 17 00:00:00 2001
> From: Michal Vrastil <michal.vrastil@hidglobal.com>
> Date: Tue, 3 Sep 2024 10:55:15 +0200
> Subject: [PATCH] Revert "usb: gadget: composite: fix OS descriptors w_value
> logic"
This looks odd, did you mean to put the whole commit in the mail?
Also, all tabs are gone, meaning you probably did a cut/paste thing,
please read the kernel documentation for how to use 'git send-email' to
make this simpler?
>
> This reverts commit ec6ce7075ef879b91a8710829016005dc8170f17.
>
> Fix install of WinUSB dsriver using OS descriptors. Without the fix the drivers are not installed correctly
> and the property 'DeviceInterfaceGUID' is missing on host side.
>
> The original change was based on assumption that the interface number is in the high byte of wValue but it is in the low byte, instead.
> Unfortunately, the fix is based on MS documentation which is also wrong.
Please wrap your changelog text at 72 columns like your editor tried to
get you to do :)
>
> The actual USB request for OS descriptors (using USB analyzer) looks like:
>
> Offset 0 1 2 3 4 5 6 7
> 0x000 C1 A1 02 00 05 00 0A 00
>
> C1: bmRequestType (device to host, vendor, interface)
> A1: nas magic number
> 0002: wValue (2: nas interface)
> 0005: wIndex (5: get extended property i.e. nas interface GUID)
> 008E: wLength (142)
>
> The fix was tested on Windows 10 and Windows 11.
>
> Signed-off-by: Michal Vrastil <michal.vrastil@hidglobal.com>
What commit id does this fix?
thanks,
greg k-h
next prev parent reply other threads:[~2024-09-03 11:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <AS8PR05MB84857AB3DC49395AEC7C235990932@AS8PR05MB8485.eurprd05.prod.outlook.com>
2024-09-03 11:14 ` [PATCH] usb: gadget: composite: fix OS descriptors w_value logic Vrastil, Michal
2024-09-03 11:23 ` Greg KH [this message]
2024-09-04 15:01 ` [PATCH] Revert "usb: gadget: composite: fix OS descriptors w_value Vrastil, Michal
2024-09-04 17:18 ` Greg KH
2024-09-04 17:31 ` Sergei Shtylyov
2024-09-04 18:19 ` Peter Korsgaard
2024-04-04 10:06 [PATCH] usb: gadget: composite: fix OS descriptors w_value logic Peter Korsgaard
2024-04-22 19:09 ` Andrzej Pietrasiewicz
2024-04-23 6:50 ` Peter Korsgaard
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=2024090305-harmonica-strained-ed09@gregkh \
--to=greg@kroah.com \
--cc=linux-usb@vger.kernel.org \
--cc=michal.vrastil@hidglobal.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;
as well as URLs for NNTP newsgroup(s).