All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michal Kazior <michal.kazior@tieto.com>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] Anyone tried using the QCA9880 NIC from the TPLINK AC1750 AP?
Date: Thu, 27 Jun 2013 07:55:52 +0200	[thread overview]
Message-ID: <CA+BoTQmHWEEx+BoN8Vncap9J9k5xPo0gSHy4j+a0Wmjh0b0Kdg@mail.gmail.com> (raw)
In-Reply-To: <51CBADFA.4050008@candelatech.com>

On 27 June 2013 05:14, Ben Greear <greearb@candelatech.com> wrote:
> 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?

There's no v1 firmware available at Kalle's github repo
(https://github.com/kvalo/ath10k-firmware) at this point. So you
either need to extract it from the AP (and hope the ABI is compatible)
or escalate the issue.



Pozdrawiam / Best Regards,
Micha? Kazior

  parent reply	other threads:[~2013-06-27  5:55 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
2013-06-27  5:33         ` Sujith Manoharan
2013-06-27  5:55         ` Michal Kazior [this message]
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
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=CA+BoTQmHWEEx+BoN8Vncap9J9k5xPo0gSHy4j+a0Wmjh0b0Kdg@mail.gmail.com \
    --to=michal.kazior@tieto.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.