From: Ping-Ke Shih <pkshih@realtek.com>
To: Bitterblue Smith <rtl8821cerfe2@gmail.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Cc: Jes Sorensen <Jes.Sorensen@gmail.com>, Jiajie Chen <c@jia.je>
Subject: RE: [PATCH v3] wifi: rtl8xxxu: Support new chip RTL8710BU aka RTL8188GU
Date: Tue, 14 Mar 2023 01:12:31 +0000 [thread overview]
Message-ID: <3e22072f0a304779b3c7914a121fedb6@realtek.com> (raw)
In-Reply-To: <4edbe29f-00b9-8eef-9789-20bed0b141e2@gmail.com>
> -----Original Message-----
> From: Bitterblue Smith <rtl8821cerfe2@gmail.com>
> Sent: Monday, March 13, 2023 9:58 PM
> To: linux-wireless@vger.kernel.org
> Cc: Jes Sorensen <Jes.Sorensen@gmail.com>; Ping-Ke Shih <pkshih@realtek.com>; Jiajie Chen <c@jia.je>
> Subject: [PATCH v3] wifi: rtl8xxxu: Support new chip RTL8710BU aka RTL8188GU
>
> This chip is found in cheap "free driver" USB adapters from Aliexpress.
> Initially they pretend to be a CD-ROM containing the driver for Windows.
> "Ejecting" switches the device to wifi mode.
>
> Features: 2.4 GHz, b/g/n mode, 1T1R, 150 Mbps.
>
> This chip is more unique than other Realtek chips:
>
> * The registers at addresses 0x0-0xff, which all the other chips use,
> can't be used here. New registers at 0x8000-0x80ff must be used
> instead. And it's not a simple matter of adding 0x8000: 0x2
> (REG_SYS_FUNC) became 0x8004, 0x80 (REG_MCU_FW_DL) became 0x8090,
> etc.
>
> * Also there are a few new registers which must be accessed indirectly
> because their addresses don't fit in 16 bits. No other chips seem to
> have these.
>
> * The vendor driver compiles to 8188gu.ko, but the code calls the chip
> RTL8710B(U) pretty much everywhere, including messages visible to the
> user.
>
> Another difference compared to the other chips supported by rtl8xxxu is
> that it has a new PHY status struct, or three of them actually, from
> which we extract the RSSI, among other things. This is not unique,
> though, just new. The chips supported by rtw88 also use it.
>
> Signed-off-by: Bitterblue Smith <rtl8821cerfe2@gmail.com>
Thanks for this nice work.
Reviewed-by: Ping-Ke Shih <pkshih@realtek.com>
next prev parent reply other threads:[~2023-03-14 1:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-13 13:58 [PATCH v3] wifi: rtl8xxxu: Support new chip RTL8710BU aka RTL8188GU Bitterblue Smith
2023-03-14 1:12 ` Ping-Ke Shih [this message]
2023-03-14 21:27 ` philipp hortmann
2023-03-20 5:54 ` Kalle Valo
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=3e22072f0a304779b3c7914a121fedb6@realtek.com \
--to=pkshih@realtek.com \
--cc=Jes.Sorensen@gmail.com \
--cc=c@jia.je \
--cc=linux-wireless@vger.kernel.org \
--cc=rtl8821cerfe2@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.