From: Jouni Malinen <j@w1.fi>
To: Ben Greear <greearb@candelatech.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: RFC: mac80211/ath9k: allow scanning single channel if other VIF is associated.
Date: Wed, 15 Sep 2010 10:31:33 -1000 [thread overview]
Message-ID: <20100915203133.GA14541@jm.kir.nu> (raw)
In-Reply-To: <4C9059DC.7060009@candelatech.com>
On Tue, Sep 14, 2010 at 10:30:04PM -0700, Ben Greear wrote:
> I think for the multi-VIF scenario, it should scan the single associated
> channel by default, but it would be nice to allow full scans on demand.
> (I would very much like to work with standard wpa_supplicant, but if hacking it
> is the only way, then I can attempt that.)
"Standard wpa_supplicant" needs to become more aware of multiple users
of the same radio, so it is certainly fine to add changes there. For
example, a mechanism for noticing that interfaces are sharing a radio
would be useful. With that, it should also be possible to share the BSS
table and scan results (and requests!) within wpa_supplicant.
Sure, mac80211 could potentially do some of merging and reusing, too,
but as far as wpa_supplicant use cases (including hostapd and AP mode in
Wi-Fi P2P like use cases here) are concerned, mac80211 changes may not
be needed for handling the scanning part.
--
Jouni Malinen PGP id EFC895FA
next prev parent reply other threads:[~2010-09-15 20:31 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-13 23:14 RFC: mac80211/ath9k: allow scanning single channel if other VIF is associated Ben Greear
2010-09-15 3:03 ` Jouni Malinen
2010-09-15 5:30 ` Ben Greear
2010-09-15 5:46 ` Dan Williams
2010-09-15 5:48 ` Dan Williams
2010-09-15 5:49 ` Ben Greear
2010-09-15 10:16 ` Johannes Berg
2010-09-15 14:21 ` Ben Greear
2010-09-15 14:24 ` Johannes Berg
2010-09-15 15:32 ` Ben Greear
2010-09-15 15:37 ` Johannes Berg
2010-09-15 16:12 ` Ben Greear
2010-09-15 20:31 ` Jouni Malinen [this message]
2010-09-15 21:04 ` Luis R. Rodriguez
2010-09-16 0:11 ` 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=20100915203133.GA14541@jm.kir.nu \
--to=j@w1.fi \
--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).