From: Kalle Valo <kvalo@codeaurora.org>
To: <yhchuang@realtek.com>
Cc: <johannes@sipsolutions.net>, <Larry.Finger@lwfinger.net>,
<pkshih@realtek.com>, <tehuang@realtek.com>,
<briannorris@chromium.org>, <sgruszka@redhat.com>,
<linux-wireless@vger.kernel.org>
Subject: Re: [PATCH v3 00/13] rtw88: mac80211 driver for Realtek 802.11ac wireless network chips
Date: Mon, 28 Jan 2019 10:36:32 +0200 [thread overview]
Message-ID: <87tvht18mn.fsf@codeaurora.org> (raw)
In-Reply-To: <1548654407-28469-1-git-send-email-yhchuang@realtek.com> (yhchuang@realtek.com's message of "Mon, 28 Jan 2019 13:46:34 +0800")
<yhchuang@realtek.com> writes:
> From: Yan-Hsuan Chuang <yhchuang@realtek.com>
>
> This is a new mac80211 driver for Realtek 802.11ac wireless network chips.
> rtw88 supports 8822BE and 8822CE chips, and will be able to support
> multi-vif combinations in run-time.
>
> For now, only PCI bus is supported, but rtw88 was originally designed
> to optionally support three buses includes USB & SDIO. USB & SDIO modules
> will soon be supported by rtw88, with configurable core module to fit
> with different bus modules in the same time.
>
> For example, if we choose 8822BE and 8822CU, only PCI & USB modules will
> be selected, built, loaded into kernel. This is one of the major
> difference from rtlwifi, which can only support specific combinations.
>
> Another difference from rtlwifi is that rtw88 is designed to support
> the latest Realtek 802.11ac wireless network chips like 8822B and
> 8822C series. Compared to the earlier chips supported by rtlwifi like
> the 802.11n 8192EE chipset or 802.11ac 8821AE/8812AE chips, newer ICs
> have different MAC & PHY settings, such as new multi-port feature for the
> MAC layer design and Jaguar2/Jaguar3 PHY layer IPs.
>
> Multi-Port feature is also supported under rtw88's software architecture.
> rtlwifi can only support one vif in the same time, most because of the
> hardware limitations for early chips, hence the original design of it
> also restricts the usage of multi-vif support, so latest chipset seems not
> take advantages from its new MAC engine.
>
> However, rtw88 can run multiple vifs concurrently by holding them on
> hardware ports provided by MAC engine, hence can easily start different
> roles on a single device.
>
> Based on the reasons mentioned before, we implemented rtw88. It had many
> authors, they are listed here alphabetically:
>
> Ping-Ke Shih <pkshih@realtek.com>
> Tzu-En Huang <tehuang@realtek.com>
> Yan-Hsuan Chuang <yhchuang@realtek.com>
>
>
> v2
>
> - add comment for watch dog
>
>
> v3
>
> - change tree location to wireless-next
What does this mean? wireless-next has not been used for years, do you
mean wireless-drivers-next instead?
--
Kalle Valo
next prev parent reply other threads:[~2019-01-28 8:36 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-28 5:46 [PATCH v3 00/13] rtw88: mac80211 driver for Realtek 802.11ac wireless network chips yhchuang
2019-01-28 5:46 ` [PATCH v3 01/13] rtw88: main files yhchuang
2019-01-28 5:46 ` [PATCH v3 02/13] rtw88: core files yhchuang
2019-01-28 5:46 ` [PATCH v3 03/13] rtw88: hci files yhchuang
2019-01-28 5:46 ` [PATCH v3 04/13] rtw88: trx files yhchuang
2019-01-28 5:46 ` [PATCH v3 05/13] rtw88: mac files yhchuang
2019-01-28 5:46 ` [PATCH v3 06/13] rtw88: fw and efuse files yhchuang
2019-01-28 5:46 ` [PATCH v3 07/13] rtw88: phy files yhchuang
2019-01-28 5:46 ` [PATCH v3 08/13] rtw88: debug files yhchuang
2019-01-28 5:46 ` [PATCH v3 09/13] rtw88: chip files yhchuang
2019-01-28 5:46 ` [PATCH v3 10/13] rtw88: 8822B init table yhchuang
2019-01-28 5:46 ` [PATCH v3 11/13] rtw88: 8822C " yhchuang
2019-01-28 5:46 ` [PATCH v3 12/13] rtw88: Kconfig & Makefile yhchuang
2019-01-28 5:46 ` [PATCH v3 13/13] rtw88: add support for Realtek 802.11ac wireless chips yhchuang
2019-01-28 8:36 ` Kalle Valo [this message]
2019-01-28 9:25 ` [PATCH v3 00/13] rtw88: mac80211 driver for Realtek 802.11ac wireless network chips Tony Chuang
2019-01-28 10:12 ` Stanislaw Gruszka
2019-01-28 22:38 ` Brian Norris
2019-01-29 2:27 ` Tony Chuang
2019-01-28 20:56 ` Larry Finger
2019-01-29 2:15 ` Tony Chuang
2019-01-29 2:41 ` Brian Norris
2019-01-29 2:53 ` Tony Chuang
2019-01-29 7:53 ` Kalle Valo
2019-01-29 3:23 ` Larry Finger
2019-01-29 4:03 ` Tony Chuang
2019-01-29 7:59 ` Kalle Valo
2019-01-29 13:01 ` Tony Chuang
2019-01-29 17:23 ` Kalle Valo
2019-01-29 14:54 ` Larry Finger
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=87tvht18mn.fsf@codeaurora.org \
--to=kvalo@codeaurora.org \
--cc=Larry.Finger@lwfinger.net \
--cc=briannorris@chromium.org \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=pkshih@realtek.com \
--cc=sgruszka@redhat.com \
--cc=tehuang@realtek.com \
--cc=yhchuang@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).