From: Johannes Berg <johannes@sipsolutions.net>
To: "Luis R. Rodriguez" <lrodriguez@atheros.com>
Cc: linville@tuxdriver.com, linux-wireless@vger.kernel.org
Subject: Re: [PATCH v2 2/5] cfg80211: enable 5 GHz world roaming channels
Date: Mon, 23 Feb 2009 17:57:31 -0800 [thread overview]
Message-ID: <1235440651.4455.49.camel@johannes.local> (raw)
In-Reply-To: <1235193641-17993-3-git-send-email-lrodriguez@atheros.com>
[-- Attachment #1: Type: text/plain, Size: 449 bytes --]
On Sat, 2009-02-21 at 00:20 -0500, Luis R. Rodriguez wrote:
> The current static world regulatory domain is too restrictive,
> we can use some 5 GHz channels world wide so long as they do not
> touch frequencies which require DFS. The compromise is we must
> also enforce passive scanning and disallow usage of a mode of
> operation that beacons: (AP | IBSS | Mesh)
We should actually start enforcing no-mesh on those channels.
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2009-02-24 2:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-21 5:20 [PATCH v2 0/5] cfg80211: enhance world roaming Luis R. Rodriguez
2009-02-21 5:20 ` [PATCH v2 1/5] cfg80211: enable active-scan / beaconing on Ch 1-11 for world regdom Luis R. Rodriguez
2009-02-21 5:20 ` [PATCH v2 2/5] cfg80211: enable 5 GHz world roaming channels Luis R. Rodriguez
2009-02-24 1:57 ` Johannes Berg [this message]
2009-02-21 5:20 ` [PATCH v2 3/5] cfg80211: Add AP beacon regulatory hints Luis R. Rodriguez
2009-02-24 1:58 ` Johannes Berg
2009-02-24 2:29 ` Luis R. Rodriguez
2009-02-24 2:47 ` Johannes Berg
2009-02-21 5:20 ` [PATCH v2 4/5] ath9k: follow beacon hints on reg_notifier when world roaming Luis R. Rodriguez
2009-02-21 5:20 ` [PATCH v2 5/5] cfg80211: default OLD_REG to n 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=1235440651.4455.49.camel@johannes.local \
--to=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=lrodriguez@atheros.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;
as well as URLs for NNTP newsgroup(s).