From: Nikolay Makarov <opnmakarov@gmail.com>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] CSI support
Date: Sun, 10 Mar 2013 13:43:57 +0400 [thread overview]
Message-ID: <-2097551306151576445@unknownmsgid> (raw)
In-Reply-To: <CAJ-VmokttY58L8hVaM0u6mDo4gkSbWRog3NQV9Do9t7uVYwpGQ@mail.gmail.com>
Thank you very much Adrian. I would appreciate your help.
? ?????????,
??????? ???????
+7 (926) 284 80 81
On 10.03.2013, at 10:21, Adrian Chadd <adrian@freebsd.org> wrote:
> On 8 March 2013 23:16, Nikolay Makarov <nmakarov@live.ru> wrote:
>> Sorry. My bad.
>>
>> The CSI (channel state information) is similar to RSSI which describes the
>> power of received signal. But unlike RSSI, CSI is energy over multiple
>> subcarriers. In 802.11 g/n, there are 64 subcarriers. So CSI is a vector
>> with 64 elements, each is a complex value. At the physical layer of wifi,
>> they will do channel estimation, CSI is the channel estimation results for
>> every subcarrier.
>
> Oh, right. Yes. I think there's a way to get the CSI out of the hardware.
> I don't know any ETA for that though; sorry.
>
> I'll poke some people to see if I can get some documentation about how
> to get CSI values and how to interpret them.
>
> Thanks,
>
>
>
> Adrian
next prev parent reply other threads:[~2013-03-10 9:43 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-07 11:30 [ath9k-devel] CSI support Nikolay Makarov
2013-03-07 23:44 ` Adrian Chadd
2013-03-09 7:16 ` Nikolay Makarov
2013-03-10 6:20 ` Adrian Chadd
2013-03-10 9:43 ` Nikolay Makarov [this message]
2013-04-02 9:52 ` Andrés García Saavedra
2013-04-02 12:18 ` Nikolay Makarov
[not found] <51C9BF5E.10607@mailservices.uwaterloo.ca>
2013-06-25 16:04 ` Ali Abedi
2013-08-16 3:46 ` Peizhao Hu
-- strict thread matches above, loose matches on Subject: below --
2013-06-27 7:24 Wai Kay
2013-07-25 17:57 Ali Abedi
2013-08-15 7:52 [ath9k-devel] CSI Support Kamran Nishat
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=-2097551306151576445@unknownmsgid \
--to=opnmakarov@gmail.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.