Search Linux Wireless

RE: [PATCH v3 00/13] rtw88: mac80211 driver for Realtek 802.11ac wireless network chips

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 




> -----Original Message-----
> From: Kalle Valo [mailto:kvalo@xxxxxxxxxxxxxx]
> Sent: Monday, January 28, 2019 4:37 PM
> To: Tony Chuang
> Cc: johannes@xxxxxxxxxxxxxxxx; Larry.Finger@xxxxxxxxxxxx; Pkshih; Andy Huang;
> briannorris@xxxxxxxxxxxx; sgruszka@xxxxxxxxxx;
> linux-wireless@xxxxxxxxxxxxxxx
> Subject: Re: [PATCH v3 00/13] rtw88: mac80211 driver for Realtek 802.11ac
> wireless network chips
> 
> <yhchuang@xxxxxxxxxxx> writes:
> 
> > From: Yan-Hsuan Chuang <yhchuang@xxxxxxxxxxx>
> >
> > 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@xxxxxxxxxxx>
> > Tzu-En Huang <tehuang@xxxxxxxxxxx>
> > Yan-Hsuan Chuang <yhchuang@xxxxxxxxxxx>
> >
> >
> > 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

Sorry for the typo here. Yes, I mean " wireless-drivers-next ".
In MAINTAINERS file, I do change to "wireless-drivers-next" instead of "wireless-next".

Yan-Hsuan





[Index of Archives]     [Linux Host AP]     [ATH6KL]     [Linux Wireless Personal Area Network]     [Linux Bluetooth]     [Wireless Regulations]     [Linux Netdev]     [Kernel Newbies]     [Linux Kernel]     [IDE]     [Git]     [Netfilter]     [Bugtraq]     [Yosemite Hiking]     [MIPS Linux]     [ARM Linux]     [Linux RAID]

  Powered by Linux