From: Alan Stern <stern@rowland.harvard.edu>
To: Zenm Chen <zenmchen@gmail.com>
Cc: gregkh@linuxfoundation.org, linux-usb@vger.kernel.org,
usb-storage@lists.one-eyed-alien.net,
linux-kernel@vger.kernel.org, pkshih@realtek.com,
rtl8821cerfe2@gmail.com, usbwifi2024@gmail.com,
stable@vger.kernel.org
Subject: Re: [PATCH] USB: storage: Ignore driver CD mode for Realtek multi-mode Wi-Fi dongles
Date: Wed, 13 Aug 2025 12:58:54 -0400 [thread overview]
Message-ID: <ff043574-e479-4a56-86a4-feaa35877d1a@rowland.harvard.edu> (raw)
In-Reply-To: <20250813162415.2630-1-zenmchen@gmail.com>
On Thu, Aug 14, 2025 at 12:24:15AM +0800, Zenm Chen wrote:
> Many Realtek USB Wi-Fi dongles released in recent years have two modes:
> one is driver CD mode which has Windows driver onboard, another one is
> Wi-Fi mode. Add the US_FL_IGNORE_DEVICE quirk for these multi-mode devices.
> Otherwise, usb_modeswitch may fail to switch them to Wi-Fi mode.
There are several other entries like this already in the unusual_devs.h
file. But I wonder if we really still need them. Shouldn't the
usb_modeswitch program be smart enough by now to know how to handle
these things?
In theory, someone might want to access the Windows driver on the
emulated CD. With this quirk, they wouldn't be able to.
Alan Stern
next prev parent reply other threads:[~2025-08-13 16:58 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-13 16:24 [PATCH] USB: storage: Ignore driver CD mode for Realtek multi-mode Wi-Fi dongles Zenm Chen
2025-08-13 16:58 ` Alan Stern [this message]
2025-08-13 17:53 ` Zenm Chen
[not found] ` <8560A878-1EAE-4FE3-B96E-2916E27F90F5@gmail.com>
2025-08-13 18:13 ` Giorgi
2025-08-13 23:32 ` Zenm Chen
2025-08-13 18:19 ` [usb-storage] " Alan Stern
2025-08-13 22:54 ` Zenm Chen
2025-08-14 1:57 ` Lars Melin
2025-08-14 14:31 ` Zenm Chen
2025-08-14 14:59 ` Zenm Chen
2025-08-14 14:03 ` Zenm Chen
2025-08-14 16:21 ` [usb-storage] " Alan Stern
2025-08-14 17:06 ` Greg KH
2025-08-14 17:22 ` Zenm Chen
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=ff043574-e479-4a56-86a4-feaa35877d1a@rowland.harvard.edu \
--to=stern@rowland.harvard.edu \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=pkshih@realtek.com \
--cc=rtl8821cerfe2@gmail.com \
--cc=stable@vger.kernel.org \
--cc=usb-storage@lists.one-eyed-alien.net \
--cc=usbwifi2024@gmail.com \
--cc=zenmchen@gmail.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