From: "Imre Kaloz" <kaloz@openwrt.org>
To: "David Lin" <dlin@marvell.com>, "Jonas Gorski" <jogo@openwrt.org>,
"Chor Teck Law" <ctlaw@marvell.com>
Cc: "Johannes Berg" <johannes@sipsolutions.net>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"Pete Hsieh" <peteh@marvell.com>
Subject: Re: [PATCH v5] Add new mac80211 driver mwlwifi.
Date: Tue, 07 Jul 2015 16:35:56 +0200 [thread overview]
Message-ID: <op.x1eqt6132s3iss@ecaz> (raw)
In-Reply-To: <82abdac15d6a469082af54661922f50c@SC-EXCH03.marvell.com>
On Tue, 07 Jul 2015 15:48:38 +0200, Chor Teck Law <ctlaw@marvell.com>
wrote:
>> >> Will change the title from "Marvell Wireless Wi-Fi driver (mwlwifi)"
>> >> to "Marvell 88W8864/88W8897 PCIe driver with AP support".
>> >
>> > As Imre pointed out, mwifiex also supports AP mode, so this is not a
>> > good description.
>
> We have explained a few times on this... Pls read about the difference
> of mwifiex vs mwlwifi. There is a NOTE added to the description of
> KConfig of mwlwifi.
>
> Would the community prefer this description instead: "Marvell
> 88W8864/88W8897 driver with MAC80211 support"?
I have a different suggestion, please read below.
>> On the short run, changing the description of the drivers could work,
>> but I would suggest dropping (at least) 8897 support from mwifiex in
>> favor of mwlwifi. If supporting the 8766 isn't complicated, I would
>> drop PCIe support completely from there.
>>
>> David, Chor Teck, could you shed some light on the future driver
>> strategy?
>
> The mwlwifi as it is today, only supports said PCIe devices. There is no
> near term plan for any other devices. But we cannot speak for future.
> Let's comment based on the current state.
Sure thing, what I was talking about is more like making the driver
selection less confusing for the enduser.
What I would propose is something along the lines (I have to cheat a bit,
I know):
mwlwifi: "Marvell Avastar (802.11ac) PCIe support"
mwifiex: "Marvell Avastar (802.11n) support"
mwl8k : "Marvell TopDog (802.11n) support"
Imre
PS:
Cheating as in mwl8k supports the 8764 Avastar radio and mwifiex supports
11ac, but well...
next prev parent reply other threads:[~2015-07-07 14:36 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-03 6:10 [PATCH v5] Add new mac80211 driver mwlwifi David Lin
2015-07-03 9:51 ` Johannes Berg
2015-07-08 0:14 ` David Lin
2015-07-04 10:40 ` Jonas Gorski
2015-07-05 10:33 ` Johannes Berg
2015-07-05 10:57 ` Jonas Gorski
2015-07-07 1:47 ` David Lin
2015-07-07 9:38 ` Jonas Gorski
2015-07-07 9:50 ` Imre Kaloz
2015-07-07 13:48 ` Chor Teck Law
2015-07-07 14:20 ` Jonas Gorski
2015-07-07 14:35 ` Imre Kaloz [this message]
2015-07-07 14:56 ` Chor Teck Law
2015-07-09 15:27 ` Maxime Bizon
2015-08-04 17:02 ` Kalle Valo
2015-08-04 18:11 ` Chor Teck Law
2015-08-04 22:49 ` Maxime Bizon
2015-09-07 10:37 ` Kalle Valo
2015-08-04 22:09 ` Maxime Bizon
2015-08-05 8:39 ` Chor Teck Law
2015-08-05 14:21 ` Maxime Bizon
2015-08-05 15:29 ` Chor Teck Law
2015-09-07 11:20 ` Kalle Valo
2015-09-11 13:43 ` Chor Teck Law
2015-09-29 9:03 ` Kalle Valo
2015-09-29 10:11 ` Kalle Valo
2015-09-30 2:05 ` David Lin
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=op.x1eqt6132s3iss@ecaz \
--to=kaloz@openwrt.org \
--cc=ctlaw@marvell.com \
--cc=dlin@marvell.com \
--cc=jogo@openwrt.org \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=peteh@marvell.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).