From: Johannes Berg <johannes@sipsolutions.net>
To: greearb@candelatech.com
Cc: linux-wireless@vger.kernel.org
Subject: Re: [RFC ] wireless: Support can-scan-one logic.
Date: Thu, 12 May 2011 10:26:31 +0200 [thread overview]
Message-ID: <1305188791.3461.6.camel@jlt3.sipsolutions.net> (raw)
In-Reply-To: <1305057374-9875-1-git-send-email-greearb@candelatech.com> (sfid-20110510_215629_728045_43BAA3DE)
On Tue, 2011-05-10 at 12:56 -0700, greearb@candelatech.com wrote:
> From: Ben Greear <greearb@candelatech.com>
>
> Enable this by passing a -1 for a scan frequency.
>
> When enabled, the system will only scan the current active
> channel if at least one VIF is actively using it. If no
> VIFS are active or this flag is disabled, then default
> behaviour is used.
>
> This helps when using multiple STA interfaces that otherwise might
> constantly be trying to scan all channels.
I still don't see what stops you from doing this in userspace, I don't
remember a compelling reason for implementing this in the kernel.
Clearly, you need to modify userspace anyhow. Also, what if, in the
future, we have multiplel STA interfaces on different channels? Which
one(s) should it pick then? The -1 trick will also break all
non-mac80211 drivers, or maybe simply not work?
johannes
next prev parent reply other threads:[~2011-05-12 8:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-10 19:56 [RFC ] wireless: Support can-scan-one logic greearb
2011-05-10 19:58 ` Ben Greear
2011-05-10 19:59 ` Daniel Halperin
2011-05-10 20:06 ` Ben Greear
2011-05-12 8:26 ` Johannes Berg [this message]
2011-05-12 16:43 ` 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=1305188791.3461.6.camel@jlt3.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=greearb@candelatech.com \
--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).