From: Adrian Chadd <adrian@freebsd.org>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] antenna-chain selection in ath9k?
Date: Thu, 7 Jul 2016 17:15:45 -0700 [thread overview]
Message-ID: <CAJ-VmomJVB2mrKxPirEA_6CqV3_8=mjpVpfGa_iFUqGS=2JUPg@mail.gmail.com> (raw)
In-Reply-To: <CACfn7v7qd_T4_LVxgujfeggh=a5NXkKamThfmE49L45JcBn5Qw@mail.gmail.com>
Hi,
I don't /think/ the CSI dump provides vectors establishing which
stream(s) appear on which antennas (ie, for stream TX 0, the
per-RX-antenna information.) It's just a magnitude value.
(I'm about to go pull down this stuff and look at it in more detail
because I just got Osprey location service stuff going in
linux/freebsd and the last bit is the CSI information..> :-)
-a
On 7 July 2016 at 12:19, Jeon <sjeon87+ath9k@gmail.com> wrote:
> I am trying to measure and compare channel state information (CSI) with both
> ath9k (AR9000 802.11n series) and iwlwifi (Intel WiFi 5300)
>
> To extract CSI, I am using
> - ath9k: Atheros CSI Tool [1]
> - iwlwifi: linux 802.11n CSI tool [2]
>
> FAQ section of iwlwifi says that, it reports permutation vector. That is, a
> signal from an antenna 1 does not always go into an rx chain 1, it can go a
> chain 2 or 3 [3]. Permutation vector tells such information.
>
> What I wonder is, does it apply same to ath9k. Currently, [1] does not
> provide such information.
>
> Regards,
> Jeon.
>
> [1] http://pdcc.ntu.edu.sg/wands/Atheros/
> [2] http://dhalperi.github.io/linux-80211n-csitool/
> [3] http://dhalperi.github.io/linux-80211n-csitool/faq.html, item #2
>
> _______________________________________________
> ath9k-devel mailing list
> ath9k-devel at lists.ath9k.org
> https://lists.ath9k.org/mailman/listinfo/ath9k-devel
>
prev parent reply other threads:[~2016-07-08 0:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-07 19:19 [ath9k-devel] antenna-chain selection in ath9k? Jeon
2016-07-08 0:15 ` Adrian Chadd [this message]
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='CAJ-VmomJVB2mrKxPirEA_6CqV3_8=mjpVpfGa_iFUqGS=2JUPg@mail.gmail.com' \
--to=adrian@freebsd.org \
--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 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 read-only IMAP folder(s) and NNTP newsgroup(s).