From: Johannes Berg <johannes-cdvu00un1VgdHxzADdlk8Q@public.gmane.org>
To: "radiotap-sUITvd46vNxg9hUCZPvPmw@public.gmane.org"
<radiotap-sUITvd46vNxg9hUCZPvPmw@public.gmane.org>
Subject: multi-antenna handling
Date: Mon, 20 Aug 2012 18:50:25 +0200 [thread overview]
Message-ID: <1345481425.4459.46.camel@jlt3.sipsolutions.net> (raw)
Hi,
This isn't really a proposal for a field definition, but more a usage
clarification that I'm seeking.
When we have multiple RX chains, it is often useful to know how much
power was received by each chain, and which chain(s) a frame was
received on.
Today, many drivers give the maximum power over all chains as a single
value, and some drivers give no antenna information while other drivers
(ab)use the (unitless) antenna index field (bit 11) as an antenna
bitmap.
I'm planning to modify this (in Linux) to include, where available,
antenna index & per-antenna signal information by duplicating the
radiotap namespace for each antenna, so that the header would, for
example, read as follows for a 3x3 devices:
* ... TSF, Flags, Rate, Channel, ...
* antenna signal: -40 dBm
* antenna: 0
* ... MCS, A-MPDU status, ...
* antenna signal: -45 dBm
* antenna: 1
* antenna signal: -43 dBm
* antenna: 2
Does this seem like sane behaviour? If so, do you think it would be
worthwhile describing it somewhere on the wiki?
johannes
next reply other threads:[~2012-08-20 16:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-20 16:50 Johannes Berg [this message]
[not found] ` <1345481425.4459.46.camel-8upI4CBIZJIJvtFkdXX2HixXY32XiHfO@public.gmane.org>
2013-07-08 8:59 ` multi-antenna handling Johannes Berg
[not found] ` <1373273952.8312.7.camel-8Nb76shvtaUJvtFkdXX2HixXY32XiHfO@public.gmane.org>
2014-06-25 1:53 ` Guy Harris
[not found] ` <C7AC152F-CCC4-48E7-B752-71655EFD0C58-FrUbXkNCsVf2fBVCVOL8/A@public.gmane.org>
2014-06-25 7:04 ` Johannes Berg
[not found] ` <1403679889.4140.2.camel-8Nb76shvtaUJvtFkdXX2HixXY32XiHfO@public.gmane.org>
2014-06-25 13:09 ` Matteo Cypriani
[not found] ` <20140625090901.fa121a689f823f3af1db1e3a-yxGd9NVxpOI@public.gmane.org>
2014-06-25 15:11 ` Johannes Berg
[not found] ` <1403709105.4140.13.camel-8Nb76shvtaUJvtFkdXX2HixXY32XiHfO@public.gmane.org>
2014-06-26 2:07 ` Guy Harris
[not found] ` <636CB894-79D9-4CC3-B820-833761A9666D-FrUbXkNCsVf2fBVCVOL8/A@public.gmane.org>
2014-06-26 6:20 ` Johannes Berg
[not found] ` <1403763600.4131.3.camel-8Nb76shvtaUJvtFkdXX2HixXY32XiHfO@public.gmane.org>
2014-06-26 8:24 ` Felix Fietkau
2018-12-30 21:47 ` "Overall" and per-chain signal/noise values (was Re: multi-antenna handling) Guy Harris
[not found] ` <0836AF8F-37B1-4E52-B14C-7D7B31D4C5E8-FrUbXkNCsVf2fBVCVOL8/A@public.gmane.org>
2019-01-15 13:19 ` Johannes Berg
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=1345481425.4459.46.camel@jlt3.sipsolutions.net \
--to=johannes-cdvu00un1vgdhxzaddlk8q@public.gmane.org \
--cc=radiotap-sUITvd46vNxg9hUCZPvPmw@public.gmane.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.