Hi David,

On Thu, Mar 17, 2016 at 12:23 PM, David Lin [off-list ref] wrote:

quoted

From: Julian Calaby [mailto:julian.calaby@gmail.com] Thursday, March 17, 2016 7:24 AM

Hi David,

On Thu, Nov 12, 2015 at 2:51 PM, David Lin [off-list ref] wrote:

quoted

This patch provides the mwlwifi driver for Marvell 8863, 8864 and 8897
chipsets.
This driver was developed as part of the openwrt.org project to
support Linksys WRT1900AC and is maintained on

https://github.com/kaloz/mwlwifi.

quoted

The mwlwifi driver differs from existing mwifiex driver:
o mwlwifi is a "softmac driver" using the kernel? mac802.11 subsystem
to provide full AP/Wireless Bridge functionality (routers).
o mwifiex is a "fullmac driver" which provides a comprehensive set of
client functions (laptops/embedded devices) o only mwlwifi supports
Marvell AP chip 886X series

NOTE: Users with Marvell 88W8897 chipsets currently should enable
(CONFIG=Y or M) either CONFIG_MWIFIEX or CONFIG_MWLWIFI, NOT

BOTH.

quoted

mwlwifi driver leveraged code from existing MWL8K driver in the
following areas:
- 802.11n setting for mac80211
- Functions needed to hook up to mac80211
- Interactions with mac80211 to establish BA streams
- Partial firmware APIs, some data fields
- Method to pass Rx packets to mac80211 except 11ac rates

In addition, mwlwifi driver supports:
- future scalability and future development (refactored source code)
- Marvell 802.11ac chipsets, including combo BT devices
- 802.11ac related settings and functions
- concurrent AP+STA functionalities with single firmware per chip
- firmware APIs for the supported chipset
- communicating new mac80211 settings to firmware
- Different TX/RX datapath where applicable
- A-MSDU and A-MPDU
- mac80211-based MESH (work in progress)
- Refined the code to establish BA streams

NOTE: MWLWIFI will be organized under new vendor specific
folder/marvell, as per request of the gate keeper and community.

Signed-off-by: David Lin <redacted>

It's been quite a while since this was reviewed. Do you have a new version of
the driver?

Yes we have some updates, and continue working on it. But we felt that community does not seem to be very interested in this driver, so we have not been updating the wireless org. Let us know if you are supportive and waiting for it.

My understanding was that we'd very much like the driver to be sent
upstream. From my perspective, it looked like you'd lost interest, not
us.

Thanks,

-- 
Julian Calaby

Email: julian.calaby@gmail.com
Profile: http://www.google.com/profiles/julian.calaby/