From: Kalle Valo <kvalo@codeaurora.org>
To: Ping-Ke Shih <pkshih@realtek.com>
Cc: <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH V2 00/18] rtw89: add Realtek 802.11ax driver
Date: Mon, 11 Jan 2021 14:58:32 +0200 [thread overview]
Message-ID: <87bldvtytj.fsf@codeaurora.org> (raw)
In-Reply-To: <20210104091817.15966-1-pkshih@realtek.com> (Ping-Ke Shih's message of "Mon, 4 Jan 2021 17:17:59 +0800")
Ping-Ke Shih <pkshih@realtek.com> writes:
> This driver named rtw89, which is the next generation of rtw88, supports
> Realtek 8852AE 802.11ax 2x2 chip whose new features are OFDMA, DBCC,
> Spatial reuse, TWT and BSS coloring; now some of them aren't implemented
> though.
>
> The chip architecture is entirely different from the chips supported by
> rtw88 like RTL8822CE 802.11ac chip. First of all, register address ranges
> are totally redefined, so it's impossible to reuse register definition. To
> communicate with firmware, new H2C/C2H format is proposed. In order to have
> better utilization, TX DMA flow is changed to two stages DMA. To provide
> rich RX status information, additional RX PPDU packets are added.
Thanks for the good introduction. Do note that currently there are two
new drivers before rtw89, so reviewing this will most likely take some
time.
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
next prev parent reply other threads:[~2021-01-11 12:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-04 9:17 [PATCH V2 00/18] rtw89: add Realtek 802.11ax driver Ping-Ke Shih
2021-01-04 9:18 ` [PATCH V2 01/18] rtw89: add CAM files Ping-Ke Shih
2021-01-04 9:18 ` [PATCH V2 02/18] rtw89: add BT coexistence files Ping-Ke Shih
2021-01-11 12:58 ` Kalle Valo [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-01-04 16:30 [PATCH V2 00/18] rtw89: add Realtek 802.11ax driver Thomas Backlund
2021-01-05 2:55 ` Pkshih
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=87bldvtytj.fsf@codeaurora.org \
--to=kvalo@codeaurora.org \
--cc=linux-wireless@vger.kernel.org \
--cc=pkshih@realtek.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;
as well as URLs for NNTP newsgroup(s).