> On 06/06/2015 6:01 AM, Alexis Green wrote: > Are there plans to add support for 802.11s mesh point mode? > Yes, it will be worked on in the future. Thanks, David > > On Fri, Jun 5, 2015 at 8:09 AM, David Lin <dlin@xxxxxxxxxxx> wrote: > >> On 06/05/2015 12:29 PM, Ben Greear wrote: > >> On 06/04/2015 07:41 PM, David Lin wrote: > >> >> On 06/03/2015 09:55 PM, David Lin wrote: > >> >>> Hi all, > >> >>> > >> >>> Herewith, I am submitting the Linux driver for WRT1900AC. The > >> work > >> >>> was initially developed as part of openwrt effort and maintained > >> >>> on https://github.com/kaloz/mwlwifi, thanks to the host where it > >> >>> is nurtured. > >> >>> > >> >>> Recently, I have also patched it to pass checkpatch.pl so that > >> >>> it can be qualified for mainline. > >> >>> > >> >>> This is still work in progress, with 8864 chipset more mature > >> >>> and tested, while 8897 for the similar use case is added > >> >>> recently. We will continue to maintain and enhance it. > >> >>> > >> >>> We hope the community will welcome this initial submission! > >> >> > >> >> Do you have any notes on what features this driver/NIC provides? > >> >> > >> >> Does it require firmware, and if so, is source available? > >> >> > >> > Support both 11b/g/a/n/ac AP mode, and STA mode (though the primary > >> > use case is AP). Driver matches most features in mac80211 and > >> > hostapd/supplicant. All basic securities mode have been validated. > >> > > >> > Yes, it will require firmware microcode. Matching "binary" is > >> > reprovided as a separate .bin file(s) for each chip. Source codes > >> > of chip-dependent microcode will not be provided. > >> > >> Can it do multiple virtual stations (and other virtual device combinations)? > >> > >> With ath10k, for instance, there is a complex firmware between the > >> host and the NIC hardware, so any bugs and limitations in the > >> firmware make it almost impossible to add interesting features or fix > >> bugs w/out being able to modify the firmware source. > >> > >> Any comments on how 'thick' the marvell firmware is? > >> > > Yes, the partitioning technically allows multiple logical interfaces. However, > this open source driver is not yet developed for many combinations, yet. > > > > It is hard to comment about "thickness" of the firmware :) All (most?) 802.11 > mgmt packets are handled in host driver. Think of microcode as part of > hardware or controlling/abstracting the hardware. > > > > Thanks, > > David > >> > >> -- > >> Ben Greear <greearb@xxxxxxxxxxxxxxx> > >> Candela Technologies Inc http://www.candelatech.com > > -- > > To unsubscribe from this list: send the line "unsubscribe > > linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx > > More majordomo info at http://vger.kernel.org/majordomo-info.html ��.n��������+%������w��{.n�����{���zW����ܨ}���Ơz�j:+v�����w����ޙ��&�)ߡ�a����z�ޗ���ݢj��w�f
