From: Ben Greear <greearb@candelatech.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [RFC 2/2] wireless: Report noise to /proc/net/wireless
Date: Thu, 30 Sep 2010 08:35:17 -0700 [thread overview]
Message-ID: <4CA4AE35.3050208@candelatech.com> (raw)
In-Reply-To: <1285832738.3639.3.camel@jlt3.sipsolutions.net>
On 09/30/2010 12:45 AM, Johannes Berg wrote:
> On Wed, 2010-09-29 at 16:57 -0700, greearb@candelatech.com wrote:
>
>> This adds noise reports to /proc/net/wireless again.
>
> Same comment applies here really...
>
>> + * @noise: noise, as obtained from dump_survey of index 0.
>
> It's not actually obtained that way, because if it was, cfg80211 could
> just handle it by itself.
>
> Additionally, even within mac80211 there's no guarantee that the
> dump_survey(0) callback will give you the correct channel's noise.
>
> Since you can easily obtain this information from userspace (and with
> the extension that Felix proposed you can figure out which noise belongs
> to the operating channel without really knowing the operating channel),
> I don't think we should be doing this.
Do you have a pointer to Felix's proposal? Maybe I can use whatever API
he came up with to populate /proc/net/wireless with the noise from the current
channel.
Thanks,
Ben
>
> johannes
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
next prev parent reply other threads:[~2010-09-30 15:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-29 23:57 [RFC 1/2] wireless: Show sta_flags for status in /proc/net/wireless greearb
2010-09-29 23:57 ` [RFC 2/2] wireless: Report noise to /proc/net/wireless greearb
2010-09-30 7:45 ` Johannes Berg
2010-09-30 15:35 ` Ben Greear [this message]
2010-09-30 7:43 ` [RFC 1/2] wireless: Show sta_flags for status in /proc/net/wireless Johannes Berg
2010-09-30 15:31 ` Ben Greear
2010-09-30 15:39 ` Johannes Berg
2010-09-30 16:49 ` Ben Greear
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=4CA4AE35.3050208@candelatech.com \
--to=greearb@candelatech.com \
--cc=johannes@sipsolutions.net \
--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).