linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ben Greear <greearb@candelatech.com>
To: David Lin <dlin@marvell.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
	Pete Hsieh <peteh@marvell.com>, Chor Teck Law <ctlaw@marvell.com>
Subject: Re: [PATCH] mwlwifi: Initial submission of wireless driver to mainline
Date: Thu, 04 Jun 2015 21:27:51 -0700	[thread overview]
Message-ID: <55712547.4010408@candelatech.com> (raw)
In-Reply-To: <a244e659293f480fb9a53ee6a83f03bf@SC-EXCH02.marvell.com>



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?

Thanks,
Ben


>
> Thanks,
> David
>

-- 
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc  http://www.candelatech.com

  reply	other threads:[~2015-06-05  4:27 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-04  4:55 [PATCH] mwlwifi: Initial submission of wireless driver to mainline David Lin
2015-06-04 15:50 ` Ben Greear
2015-06-05  2:41   ` David Lin
2015-06-05  4:27     ` Ben Greear [this message]
2015-06-05 15:09       ` David Lin
2015-06-05 22:00         ` Alexis Green
2015-06-06  1:03           ` 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=55712547.4010408@candelatech.com \
    --to=greearb@candelatech.com \
    --cc=ctlaw@marvell.com \
    --cc=dlin@marvell.com \
    --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).