From: Dan <aidan@plezica.com>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] ath9k: spectral scan -vs- channel state information
Date: Tue, 12 Apr 2016 22:05:16 +0000 (UTC) [thread overview]
Message-ID: <loom.20160412T235259-403@post.gmane.org> (raw)
Hi
I am having some trouble understanding the difference between
channel state information (often requested on the mailing list)
and what is currently available via spectral scan.
My understanding is as follows;
- spectral scan (once triggered via the debugfs) logs
channel state estimation for each of the 56 ofdm subcarriers
(HT20 case). In the spectral code (for ath9k), the channel state
info is the I and Q values for the subcarriers.
For ath9k, the bulk of the code is in ath_process_fft
Bits I dont understand :
Can channel state information be collected on a more general
basis ? --- for example for each phy packet received.
Also, the calibration (ar9003_calib) seems to gather I and Q
data also... but its not clear when this is run/collected and used.
Any help appreciated....
next reply other threads:[~2016-04-12 22:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-12 22:05 Dan [this message]
2016-04-12 22:20 ` [ath9k-devel] ath9k: spectral scan -vs- channel state information Adrian Chadd
2016-04-13 8:40 ` Dan
2016-04-13 18:52 ` Adrian Chadd
2016-05-09 1:42 ` Allen Welkie
2016-05-10 6:40 ` Robert Felten
2016-05-18 8:56 ` Dan
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=loom.20160412T235259-403@post.gmane.org \
--to=aidan@plezica.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 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).