From: Ben Greear <greearb@candelatech.com>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] Anyone tried using the QCA9880 NIC from the TPLINK AC1750 AP?
Date: Wed, 26 Jun 2013 20:14:02 -0700 [thread overview]
Message-ID: <51CBADFA.4050008@candelatech.com> (raw)
In-Reply-To: <20939.43650.235001.756470@gargle.gargle.HOWL>
On 06/26/2013 07:59 PM, Sujith Manoharan wrote:
> Ben Greear wrote:
>> Excellent! I'll go order some more! Not the most efficient way
>> to get NICs, but it will do for now.
>
> IMO, it's better to wait until the v2.0 cards are available.
Seems to be a common suggestion!
I've already got a few v1 APs on order, maybe they will
at least give me something to get started with.
If you are at liberty to say, what sorts of issues should I
expect with the v1? Or perhaps a better question: How is the
v2 expected to be better?
(I haven't seen mention of any ath10k bug reports yet,
probably because the public generally doesn't have any
NICs yet...?)
Thanks,
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
next prev parent reply other threads:[~2013-06-27 3:14 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-27 1:10 [ath9k-devel] Anyone tried using the QCA9880 NIC from the TPLINK AC1750 AP? Ben Greear
2013-06-27 1:14 ` Joel Wirāmu Pauling
2013-06-27 1:32 ` Ben Greear
2013-06-27 2:09 ` Sujith Manoharan
2013-06-27 2:20 ` Ben Greear
2013-06-27 2:59 ` Sujith Manoharan
2013-06-27 3:14 ` Ben Greear [this message]
2013-06-27 5:33 ` Sujith Manoharan
2013-06-27 5:55 ` Michal Kazior
2013-06-27 6:09 ` Sujith Manoharan
2013-06-28 7:22 ` Kalle Valo
2013-06-28 16:24 ` Ben Greear
2013-10-03 14:25 ` Konstantin Kuzov
2013-10-03 14:50 ` Adrian Chadd
2013-07-02 17:12 ` Ben Greear
2013-06-28 7:21 ` Kalle Valo
-- strict thread matches above, loose matches on Subject: below --
2013-06-27 10:04 Trevor Cullen
2013-06-27 13:35 ` Ben Greear
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=51CBADFA.4050008@candelatech.com \
--to=greearb@candelatech.com \
--cc=ath9k-devel@lists.ath9k.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.