From: Ben Greear <greearb@candelatech.com>
To: Fred Matthews <fredmm@hotmail.co.uk>
Cc: ionic@ionic.de, linux-kernel@vger.kernel.org,
linux-wireless@vger.kernel.org, ath9k-devel@venema.h4ckr.net
Subject: Re: [ath9k-devel] AR9380 current driver supported features
Date: Mon, 13 Jun 2011 11:18:26 -0700 [thread overview]
Message-ID: <4DF65472.9070601@candelatech.com> (raw)
In-Reply-To: <BLU158-w58841DE4774E18813C30CA87690@phx.gbl>
On 06/13/2011 11:09 AM, Fred Matthews wrote:
>
> Hi,I am looking to upgrade my current nodes and AP from the AR9280 2x2 MIMO NIC to the AR9380 3x3 NIC.
> Thus I was wondering if someone can kindly comment on the current chipset stability with ath9k, also the current supported features (e.g. "iw list" output) such as setting the NIC as an AP/Master using hostapd, Greenfield mode, TxBF, CSI info, and LPDC as well as rates achieved.
> Thanks in advance
Both are stable in our testing (virtual stations, AP mode), but we're having
a hard time sourcing AR9380 3x3 NICs..getting ship-times in August, etc....
I don't have details on the other things you ask about.
I'd suggest getting a few NICs and trying them out in your environment.
Even if they have problems, there are folks actively working on it and
likely it can be fixed. And at least for our use with virtual stations & APs,
there is no other NIC that comes close to the features that Atheros offers.
Thanks,
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
next prev parent reply other threads:[~2011-06-13 18:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <BLU158-w3633DDF37956A9F5672C1F87690@phx.gbl>
2011-06-13 18:09 ` AR9380 current driver supported features Fred Matthews
2011-06-13 18:18 ` Ben Greear [this message]
2011-06-13 19:10 ` [ath9k-devel] " Daniel Halperin
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=4DF65472.9070601@candelatech.com \
--to=greearb@candelatech.com \
--cc=ath9k-devel@venema.h4ckr.net \
--cc=fredmm@hotmail.co.uk \
--cc=ionic@ionic.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
/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