From: Johannes Berg <johannes@sipsolutions.net>
To: Jouni Malinen <j@w1.fi>
Cc: Holger Schurig <h.schurig@mn-solutions.de>,
linux-wireless <linux-wireless@vger.kernel.org>,
Felix Fietkau <nbd@openwrt.org>
Subject: Re: RECAP: indication of channel noise
Date: Tue, 27 Oct 2009 08:03:16 +0100 [thread overview]
Message-ID: <1256626996.4237.4.camel@johannes.local> (raw)
In-Reply-To: <20091027034514.GA20995@jm.kir.nu>
[-- Attachment #1: Type: text/plain, Size: 836 bytes --]
On Mon, 2009-10-26 at 20:45 -0700, Jouni Malinen wrote:
> On Mon, Oct 26, 2009 at 02:42:44PM +0100, Holger Schurig wrote:
>
> > The idea is to have one API call "do site survey", where you tell
> > the driver to scan on specified/all channels to determine those
> > values.
>
> What would this command be? Just the existing scan trigger command with
> a new attribute indicating that site survey is requested? In my first
> use case (select best channel for an AP), I would like to combine the
> normal scan (get all BSSes) and site survey (get tx/rx/idle hw counters
> for each channel). Fetching the site survey data with a new command
> would be fine, but trigger command should be shared.
That was my thinking (shared trigger) as well. Fetching the data cannot
be done with the same command anyway.
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 801 bytes --]
prev parent reply other threads:[~2009-10-27 7:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-26 13:42 RECAP: indication of channel noise Holger Schurig
2009-10-26 13:52 ` Johannes Berg
2009-10-26 14:30 ` Holger Schurig
2009-10-27 3:45 ` Jouni Malinen
2009-10-27 7:03 ` Johannes Berg [this message]
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=1256626996.4237.4.camel@johannes.local \
--to=johannes@sipsolutions.net \
--cc=h.schurig@mn-solutions.de \
--cc=j@w1.fi \
--cc=linux-wireless@vger.kernel.org \
--cc=nbd@openwrt.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