From: "Luis R. Rodriguez" <lrodriguez@atheros.com>
To: <johannes@sipsolutions.net>, <johannes@sipsolutions.net>,
<linville@tuxdriver.com>
Cc: "Luis R. Rodriguez" <lrodriguez@atheros.com>,
<linux-wireless@vger.kernel.org>
Subject: [RFC 0/2] cfg80211/mac80211: help world roaming through beacons reg hints
Date: Mon, 2 Feb 2009 21:01:51 -0800 [thread overview]
Message-ID: <1233637313-16786-1-git-send-email-lrodriguez@atheros.com> (raw)
This adds support to help the wireless core with world roaming
by providing hints to when we receive beacons from APs. Devices
can be world roaming when the world regulatory domain is set or
the device has a custom regulatory domain and no country IEs have
been received.
This should should help users more on 5 GHz which doesn't allow beaconing
or active scanning when world roaming.
We call mac80211's beacon hint from ieee80211_mlme_notify_scan_completed(),
which is called at the end of ieee80211_scan_completed(). This guarantees
that we take advantage of devices which do hw-scanning or sw-scanning.
Review with the locking is appreciated, but I think this is OK.
Luis R. Rodriguez (2):
wireless: add regulatory_hint_found_beacon() to make help world
roaming
ath9k: follow beacon hints on reg_notifier when world roaming
drivers/net/wireless/ath9k/regd.c | 92 ++++++++++++-------
include/net/wireless.h | 20 ++++
net/mac80211/mlme.c | 35 +++++++
net/wireless/reg.c | 181 ++++++++++++++++++++++++++++++++++++-
4 files changed, 295 insertions(+), 33 deletions(-)
next reply other threads:[~2009-02-03 5:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-03 5:01 Luis R. Rodriguez [this message]
2009-02-03 5:01 ` [RFC 1/2] cfg80211/mac80211: add regulatory_hint_found_beacon() to make help world roaming Luis R. Rodriguez
2009-02-03 5:01 ` [RFC 2/2] ath9k: follow beacon hints on reg_notifier when " Luis R. Rodriguez
2009-02-03 10:11 ` [RFC 1/2] cfg80211/mac80211: add regulatory_hint_found_beacon() to make help " Johannes Berg
2009-02-03 15:27 ` Luis R. Rodriguez
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=1233637313-16786-1-git-send-email-lrodriguez@atheros.com \
--to=lrodriguez@atheros.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
/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