From: Gerrit Renker <gerrit@sdf.org>
To: linux-wireless@vger.kernel.org
Subject: [WEXT/nl80211] few API questions
Date: Sat, 31 Oct 2015 14:10:57 -0600 [thread overview]
Message-ID: <20151031141057.324b3274@vaygach> (raw)
I have a few short nl80211 API questions to help convert a userland
program from WEXT to nl80211 [1].
The iw code has been helpful, and I have used bits of it so far. When it comes
to kernel components, though, I don't understand that code well enough; so I'd
appreciate help with the following:
1. Signal Level Units
This refers to station signal level in status ASSOCIATED, AUTHENTICATED,
or IBSS_JOINED.
Q: Are the values reported via NL80211_STA_INFO_SIGNAL{,_AVG}
in xxx always in dBm, or if not, what information should be used
(NL80211_BSS_SIGNAL_MBM, NL80211_BSS_SIGNAL_UNSPEC).
The wext API sets the unit via iw_quality.updated flags (IW_QUAL_DBM),
is the same needed in nl80211?
2. Noise Level
It seems that the WEXT API does no longer support reporting noise floor
levels (IW_QUAL_NOISE_INVALID is always set).
Q: Is it correct to use NL80211_SURVEY_INFO_NOISE for the active channel
(NL80211_SURVEY_INFO_IN_USE) as replacement (header says it is dBm)?
3. Link Quality
WEXT has the concept of a link quality metric (iw_quality.qual).
Q: Given access to signal levels in dBm or mBm, looking at
cfg80211_wireless_stats(); would be correct to replace the call to
SIOCGIWSTATS by using the nl80211 values in (1) and simply
interpret -110dBm and -40dBm as ends of a quality scale from 0..70?
Thanks in advance,
Gerrit
[1] https://github.com/uoaerg/wavemon/tree/development
next reply other threads:[~2015-10-31 20:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-31 20:10 Gerrit Renker [this message]
2015-11-02 8:37 ` [WEXT/nl80211] few API questions Johannes Berg
2015-11-03 4:10 ` Gerrit Renker
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=20151031141057.324b3274@vaygach \
--to=gerrit@sdf.org \
--cc=linux-wireless@vger.kernel.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 NNTP newsgroup(s).