From: Benoit PAPILLAULT <benoit.papillault@free.fr>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] [PATCH] ath9k: Added get_survey callback in order to get channel noise
Date: Wed, 28 Apr 2010 22:13:43 +0200 [thread overview]
Message-ID: <4BD896F7.5090703@free.fr> (raw)
In-Reply-To: <1272438045.2772.6.camel@jm-desktop>
Jouni Malinen a ?crit :
> 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
>
Hi Jouni,
I dig into the source code to understand the use of "idx" and having the
value for all scanned channels sounds a good plan. However :
- when doing a normal scan (iw dev wlan0 scan), the noise floor
calibration is started in a special mode, so I don't know if the results
is accurate enought.
- the first calibration takes some times .... more than the scan itself.
So, you cannot get a valid value before switching to the next channel.
Anyway, how idx is supposed to be used? From 0 ... up to the callback
returning -ENOENT ?
Do we need to keep a table with noise for each channel and return those
where we have a value, in which case idx cannot be used as an index into
this table ?
Regards,
Benoit
WARNING: multiple messages have this Message-ID (diff)
From: Benoit PAPILLAULT <benoit.papillault@free.fr>
To: Jouni Malinen <jouni.malinen@atheros.com>
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 22:13:43 +0200 [thread overview]
Message-ID: <4BD896F7.5090703@free.fr> (raw)
In-Reply-To: <1272438045.2772.6.camel@jm-desktop>
Jouni Malinen a écrit :
> 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
>
Hi Jouni,
I dig into the source code to understand the use of "idx" and having the
value for all scanned channels sounds a good plan. However :
- when doing a normal scan (iw dev wlan0 scan), the noise floor
calibration is started in a special mode, so I don't know if the results
is accurate enought.
- the first calibration takes some times .... more than the scan itself.
So, you cannot get a valid value before switching to the next channel.
Anyway, how idx is supposed to be used? From 0 ... up to the callback
returning -ENOENT ?
Do we need to keep a table with noise for each channel and return those
where we have a value, in which case idx cannot be used as an index into
this table ?
Regards,
Benoit
next prev parent reply other threads:[~2010-04-28 20:13 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-27 22:08 [ath9k-devel] [PATCH] ath9k: Added get_survey callback in order to get channel noise Benoit Papillault
2010-04-27 22:08 ` Benoit Papillault
2010-04-27 22:17 ` [ath9k-devel] " Luis R. Rodriguez
2010-04-27 22:17 ` Luis R. Rodriguez
2010-04-28 7:00 ` [ath9k-devel] " Jouni Malinen
2010-04-28 7:00 ` Jouni Malinen
2010-04-28 8:01 ` [ath9k-devel] kernel warning on 2.6.33 ath9k Xu, Martin
2010-04-28 8:01 ` Xu, Martin
2010-04-28 14:04 ` [ath9k-devel] " John W. Linville
2010-04-28 14:04 ` John W. Linville
2010-04-29 0:39 ` [ath9k-devel] " Xu, Martin
2010-04-29 0:39 ` Xu, Martin
2010-04-28 20:13 ` Benoit PAPILLAULT [this message]
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=4BD896F7.5090703@free.fr \
--to=benoit.papillault@free.fr \
--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.