From: Giorgi <giorgitchankvetadze1997@gmail.com>
To: Zenm Chen <zenmchen@gmail.com>, stern@rowland.harvard.edu
Cc: gregkh@linuxfoundation.org, linux-kernel@vger.kernel.org,
linux-usb@vger.kernel.org, pkshih@realtek.com,
rtl8821cerfe2@gmail.com, stable@vger.kernel.org,
usb-storage@lists.one-eyed-alien.net, usbwifi2024@gmail.com,
zenmchen@gmail.com
Subject: Re: [PATCH] USB: storage: Ignore driver CD mode for Realtek multi-mode Wi-Fi dongles
Date: Wed, 13 Aug 2025 22:13:18 +0400 [thread overview]
Message-ID: <A54117AB-2BFD-4864-AEA3-4F1AF977A869@gmail.com> (raw)
In-Reply-To: <8560A878-1EAE-4FE3-B96E-2916E27F90F5@gmail.com>
Maybe we could only add US_FL_IGNORE_DEVICE for the exact Realtek-based models (Mercury MW310UH, D-Link AX9U, etc.) that fail with usb_modeswitch.
This avoids disabling access to the emulated CD for unrelated devices.
>On August 13, 2025 9:53:12 PM GMT+04:00, Zenm Chen <zenmchen@gmail.com> wrote:
>>Alan Stern <stern@rowland.harvard.edu> 於 2025年8月14日 週四 上午12:58寫道:
>>>
>>> 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?
>>
>>Hi Alan,
>>
>>Thanks for your review and reply.
>>
>>Without this patch applied, usb_modeswitch cannot switch my Mercury MW310UH
>>into Wi-Fi mode [1]. I also ran into a similar problem like [2] with D-Link
>>AX9U, so I believe this patch is needed.
>>
>>>
>>> In theory, someone might want to access the Windows driver on the
>>> emulated CD. With this quirk, they wouldn't be able to.
>>>
>>
>>Actually an emulated CD doesn't appear when I insert these 2 Wi-Fi dongles into
>>my Linux PC, so users cannot access that Windows driver even if this patch is not
>>applied.
>>
>>> Alan Stern
>>
>>[1] https://drive.google.com/file/d/1YfWUTxKnvSeu1egMSwcF-memu3Kis8Mg/view?usp=drive_link
>>
>>[2] https://github.com/morrownr/rtw89/issues/10
>>
next prev parent reply other threads:[~2025-08-13 18:13 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
2025-08-13 17:53 ` Zenm Chen
[not found] ` <8560A878-1EAE-4FE3-B96E-2916E27F90F5@gmail.com>
2025-08-13 18:13 ` Giorgi [this message]
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=A54117AB-2BFD-4864-AEA3-4F1AF977A869@gmail.com \
--to=giorgitchankvetadze1997@gmail.com \
--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=stern@rowland.harvard.edu \
--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