From: Ping-Ke Shih <pkshih@realtek.com>
To: Zenm Chen <zenmchen@gmail.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Cc: "rtl8821cerfe2@gmail.com" <rtl8821cerfe2@gmail.com>
Subject: RE: [PATCH] wifi: rtw88: Add support for Mercusys MA30N and D-Link DWA-T185 rev. A1
Date: Tue, 11 Feb 2025 05:59:30 +0000 [thread overview]
Message-ID: <1f46070899bf4ddaa7b668a1f96b85ed@realtek.com> (raw)
In-Reply-To: <20250210073610.4174-1-zenmchen@gmail.com>
Zenm Chen <zenmchen@gmail.com> wrote:
> Add two more USB IDs found in
> https://github.com/RinCat/RTL88x2BU-Linux-Driver
> to support Mercusys MA30N and D-Link DWA-T185 rev. A1.
>
> Signed-off-by: Zenm Chen <zenmchen@gmail.com>
Acked-by: Ping-Ke Shih <pkshih@realtek.com>
> ---
> Related discussions:
> https://github.com/RinCat/RTL88x2BU-Linux-Driver/issues/237
> https://github.com/RinCat/RTL88x2BU-Linux-Driver/issues/146
> ---
> drivers/net/wireless/realtek/rtw88/rtw8822bu.c | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/drivers/net/wireless/realtek/rtw88/rtw8822bu.c
> b/drivers/net/wireless/realtek/rtw88/rtw8822bu.c
> index 8883300fc6ad..572d1f31832e 100644
> --- a/drivers/net/wireless/realtek/rtw88/rtw8822bu.c
> +++ b/drivers/net/wireless/realtek/rtw88/rtw8822bu.c
> @@ -73,6 +73,10 @@ static const struct usb_device_id rtw_8822bu_id_table[] = {
> .driver_info = (kernel_ulong_t)&(rtw8822b_hw_spec) }, /* ELECOM WDB-867DU3S */
> { USB_DEVICE_AND_INTERFACE_INFO(0x2c4e, 0x0107, 0xff, 0xff, 0xff),
> .driver_info = (kernel_ulong_t)&(rtw8822b_hw_spec) }, /* Mercusys MA30H */
> + { USB_DEVICE_AND_INTERFACE_INFO(0x2c4e, 0x010a, 0xff, 0xff, 0xff),
> + .driver_info = (kernel_ulong_t)&(rtw8822b_hw_spec) }, /* Mercusys MA30N */
> + { USB_DEVICE_AND_INTERFACE_INFO(0x2001, 0x3322, 0xff, 0xff, 0xff),
> + .driver_info = (kernel_ulong_t)&(rtw8822b_hw_spec) }, /* D-Link DWA-T185 rev. A1 */
By the way, these IDs aren't in increasing order, how did you pick IDs
from vendor driver?
Not sure if it's worth to sort these IDs so that it would be easier to
align IDs with vendor driver (it should be sorted as well).
next prev parent reply other threads:[~2025-02-11 5:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-10 7:36 [PATCH] wifi: rtw88: Add support for Mercusys MA30N and D-Link DWA-T185 rev. A1 Zenm Chen
2025-02-11 5:59 ` Ping-Ke Shih [this message]
2025-02-11 6:15 ` Zenm Chen
2025-02-11 6:20 ` Ping-Ke Shih
2025-02-21 1:27 ` 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=1f46070899bf4ddaa7b668a1f96b85ed@realtek.com \
--to=pkshih@realtek.com \
--cc=linux-wireless@vger.kernel.org \
--cc=rtl8821cerfe2@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