Historical ath9k-devel archives
 help / color / mirror / Atom feed
From: Till Wollenberg <till.wollenberg@uni-rostock.de>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] How to get CSI from Atheros Chipset
Date: Tue, 25 Aug 2015 17:42:18 +0200	[thread overview]
Message-ID: <55DC8CDA.3000106@uni-rostock.de> (raw)
In-Reply-To: <CAJ-Vmo=GWYFMnLg=-hRwe7iEPjs5qcTYJn9YaDXX-R0uVSQHxw@mail.gmail.com>

Hi Adrian,

* On 24.08.2015 18:40 Adrian Chadd wrote:
> On 24 August 2015 at 08:14, Till Wollenberg <till.wollenberg@uni-rostock.de> wrote:
>> * On 23.08.2015 at 21:57 Adrian Chadd wrote:
>>> [Getting CSI]
>>> ok, I've found a few pieces about this. What exactly are people after?
>>
>> SNR per OFDM sub-carrier for a recevied frame would be *very* interesting to me.

> ok,
>
> So the legacy bits include |I| and |Q| but it's not per-frame, it's
> set-once-and-get-next-frame. You then read bins from the NIC itself in
> some shared memory inside said NIC. I'll go see if this works on the
> earlier chips and try to get this published, at least so there's
> something to start with.

Sounds interesting. So is this per-frame information if the internal registers 
are read out right after receiving a frame, or is it always an aggregate over 
several received frames?

> I think AR9380 and later support what you saw in that paper - where
> you request that you get CSI data as part of some receive frame. I
> /think/ it's part of the TxBF support. I'll have to double-check if
> that's okay to extract and publish.

I'm not the OP so I'm not quite sure what the paper is about. Nevertheless, I 
plan to use AR9590 and/or AR9390 cards so I guess that these meet the criterion 
of "AR9380 and later".

Best
Till.

  reply	other threads:[~2015-08-25 15:42 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-22 11:52 [ath9k-devel] How to get CSI from Atheros Chipset Zeyu Wang
2015-08-13 20:06 ` Hemamali
2015-08-14  1:12   ` Adrian Chadd
2015-08-14  1:24     ` Jesse Libertine
2015-08-22 18:09     ` Hemamali G
2015-08-23 19:57       ` Adrian Chadd
2015-08-23 20:13         ` Vincent Schnitzbauer
2015-08-23 22:04           ` Adrian Chadd
2015-08-24  9:29         ` Hemamali G
2015-08-24  9:51           ` Vincent Schnitzbauer
2015-08-24  9:57             ` Hemamali G
2015-09-10 12:35               ` Hemamali G
2015-08-24 15:14         ` Till Wollenberg
2015-08-24 16:40           ` Adrian Chadd
2015-08-25 15:42             ` Till Wollenberg [this message]
     [not found] <mailman.1.1440496802.17735.ath9k-devel@lists.ath9k.org>
2015-08-25 14:15 ` Brandon Enochs

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=55DC8CDA.3000106@uni-rostock.de \
    --to=till.wollenberg@uni-rostock.de \
    --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