From: Ping-Ke Shih <pkshih@realtek.com>
To: Zenm Chen <zenmchen@gmail.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"rtl8821cerfe2@gmail.com" <rtl8821cerfe2@gmail.com>,
"stable@vger.kernel.org" <stable@vger.kernel.org>
Subject: RE: [PATCH rtw-next] wifi: rtl8xxxu: Add USB ID 2001:3328 for D-Link AN3U rev. A1
Date: Tue, 30 Sep 2025 07:57:00 +0000 [thread overview]
Message-ID: <70d9d98f2c8d41fb94438d653e91697a@realtek.com> (raw)
In-Reply-To: <20250930074530.4204-1-zenmchen@gmail.com>
Zenm Chen <zenmchen@gmail.com> wrote:
> Ping-Ke Shih <pkshih@realtek.com> 於 2025年9月30日 週二 上午11:19寫道:
> >
> > Zenm Chen <zenmchen@gmail.com> wrote:
> > > Add USB ID 2001:3328 for D-Link AN3U rev. A1 which is a RTL8192FU-based
> > > Wi-Fi adapter.
> > >
> > > Compile tested only.
> > >
> > > Cc: stable@vger.kernel.org # 6.6.x
> > > Signed-off-by: Zenm Chen <zenmchen@gmail.com>
> > > ---
> > > Link to the Windows driver for D-Link AN3U rev. A1
> > >
> > > https://www.dlinktw.com.tw/techsupport/ProductInfo.aspx?m=AN3U
> >
> > Could you please enlighten me how you address this is RTL8192FU-based?
> > I downloaded the setup.ext and decompressed the file, but I can't find
> > 8192FU.
>
> Hi Ping-Ke,
>
> After installing that Windows driver, the driver will be placed at C:\Program Files\D-Link\AN3U\Driver.
>
> According to the line 266 of the C:\Program Files\D-Link\AN3U\Driver\WIN10X64\netrtwlanu.inf file [1], we
> know that this dongle uses a 8192FU chip.
> The specification [2] which says it supports both WPA2 and WPA3 is also a clue. As far as I know, among
> all Windows drivers for Realtek 802.11n 2T2R chips, only the driver for 8192FU supports both WPA2/WPA3,
> others support WPA2 only.
> This is how I determine what chip this dongle uses, but unfortunately there is no related report at
> linux-hardware.org [3] so cannot confirm it does use the ID 2001:3328.
Thanks for the detail. I have no permission to install drivers to
my Windows PC in office, so I can only try to decompress setup.exe.
Anyway, ack this patch. Thanks.
Reviewed-by: Ping-Ke Shih <pkshih@realtek.com>
>
> [1] line 265 ~ 266 of the netrtwlanu.inf file
> ;; For 8192F DLINK
> %DLink_AN3U.DeviceDesc% = RTL8192fu.ndi, USB\VID_2001&PID_3328
>
> [2] https://www.dlink.com/tw/zh/products/an3u#Specs
>
> [3] Reports about the ID 2001:3328 and 2001:3329
> https://linux-hardware.org/?id=usb:2001-3328
> https://linux-hardware.org/?id=usb:2001-3329
>
> >
> > > ---
> > > drivers/net/wireless/realtek/rtl8xxxu/core.c | 3 +++
> > > 1 file changed, 3 insertions(+)
> > >
> > > diff --git a/drivers/net/wireless/realtek/rtl8xxxu/core.c
> > > b/drivers/net/wireless/realtek/rtl8xxxu/core.c
> > > index 3ded59527..be39463bd 100644
> > > --- a/drivers/net/wireless/realtek/rtl8xxxu/core.c
> > > +++ b/drivers/net/wireless/realtek/rtl8xxxu/core.c
> > > @@ -8136,6 +8136,9 @@ static const struct usb_device_id dev_table[] = {
> > > /* TP-Link TL-WN823N V2 */
> > > {USB_DEVICE_AND_INTERFACE_INFO(0x2357, 0x0135, 0xff, 0xff, 0xff),
> > > .driver_info = (unsigned long)&rtl8192fu_fops},
> > > +/* D-Link AN3U rev. A1 */
> > > +{USB_DEVICE_AND_INTERFACE_INFO(0x2001, 0x3328, 0xff, 0xff, 0xff),
> > > + .driver_info = (unsigned long)&rtl8192fu_fops},
> > > #ifdef CONFIG_RTL8XXXU_UNTESTED
> > > /* Still supported by rtlwifi */
> > > {USB_DEVICE_AND_INTERFACE_INFO(USB_VENDOR_ID_REALTEK, 0x8176, 0xff, 0xff, 0xff),
> > > --
> > > 2.51.0
> >
next prev parent reply other threads:[~2025-09-30 7:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-29 3:57 [PATCH rtw-next] wifi: rtl8xxxu: Add USB ID 2001:3328 for D-Link AN3U rev. A1 Zenm Chen
2025-09-29 3:57 ` [PATCH rtw-next] wifi: rtw88: Add USB ID 2001:3329 for D-Link AC13U " Zenm Chen
2025-09-30 7:59 ` Ping-Ke Shih
2025-10-21 5:39 ` Ping-Ke Shih
2025-09-30 3:19 ` [PATCH rtw-next] wifi: rtl8xxxu: Add USB ID 2001:3328 for D-Link AN3U " Ping-Ke Shih
2025-09-30 7:45 ` Zenm Chen
2025-09-30 7:57 ` Ping-Ke Shih [this message]
2025-10-21 5:34 ` Ping-Ke Shih
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=70d9d98f2c8d41fb94438d653e91697a@realtek.com \
--to=pkshih@realtek.com \
--cc=linux-wireless@vger.kernel.org \
--cc=rtl8821cerfe2@gmail.com \
--cc=stable@vger.kernel.org \
--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