From: Jouni Malinen <jouni.malinen@atheros.com>
To: Benoit Papillault <benoit.papillault@free.fr>
Cc: Luis Rodriguez <Luis.Rodriguez@Atheros.com>,
"ath9k-devel@lists.ath5k.org" <ath9k-devel@lists.ath5k.org>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH] ath9k: Added get_survey callback in order to get channel noise
Date: Wed, 28 Apr 2010 10:00:45 +0300 [thread overview]
Message-ID: <1272438045.2772.6.camel@jm-desktop> (raw)
In-Reply-To: <1272406104-6870-1-git-send-email-benoit.papillault@free.fr>
On Tue, 2010-04-27 at 15:08 -0700, Benoit Papillault wrote:
> +static int ath9k_get_survey(struct ieee80211_hw *hw, int idx,
> + struct survey_info *survey)
> + struct ieee80211_conf *conf = &hw->conf;
> +
> + if (idx != 0)
> + return -ENOENT;
> +
> + survey->channel = conf->channel;
Are there any plans on providing this information from all channels? I
have assumed that the survey command was supposed to be used for
surveying all channels (e.g., to get information for auto-channel
selection) and returning something for the current channel is quite
limited subset of that. In other words, I would like to be able to run a
scan of all channels and then use NL80211_CMD_GET_SURVEY to fetch
additional per-channel information like noise (and also channel usage
statistics in case of ath9k) from the scanned channels.
- Jouni
next prev parent reply other threads:[~2010-04-28 7:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-27 22:08 [PATCH] ath9k: Added get_survey callback in order to get channel noise Benoit Papillault
2010-04-27 22:17 ` Luis R. Rodriguez
2010-04-28 7:00 ` Jouni Malinen [this message]
2010-04-28 8:01 ` kernel warning on 2.6.33 ath9k Xu, Martin
2010-04-28 14:04 ` John W. Linville
2010-04-29 0:39 ` Xu, Martin
2010-04-28 20:13 ` [PATCH] ath9k: Added get_survey callback in order to get channel noise Benoit PAPILLAULT
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=1272438045.2772.6.camel@jm-desktop \
--to=jouni.malinen@atheros.com \
--cc=Luis.Rodriguez@Atheros.com \
--cc=ath9k-devel@lists.ath5k.org \
--cc=benoit.papillault@free.fr \
--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).