From: Johannes Berg <johannes@sipsolutions.net>
To: "Luis R. Rodriguez" <mcgrof@do-not-panic.com>
Cc: Michael Green <green@qca.qualcomm.com>, linux-wireless@vger.kernel.org
Subject: Re: [RFC 1/2] regulatory: allow arbitrary channel widths
Date: Thu, 13 Dec 2012 23:33:12 +0100 [thread overview]
Message-ID: <1355437992.9463.30.camel@jlt4.sipsolutions.net> (raw)
In-Reply-To: <CAB=NE6XbbkoWyMyjWtV6EpbT4A7MS5fZRiXgd_Pdok8eE1-e0Q@mail.gmail.com> (sfid-20121213_232850_441393_F837467A)
On Thu, 2012-12-13 at 14:28 -0800, Luis R. Rodriguez wrote:
> Oops, forgot to add Michael, adding him now.
>
> Michael, just a sanity check for you. What Johannes is saying is that
> regulatory wise for the 2.4 GHz band on channels 1-11 and on 5 GHz on
> non DFS channels where we never initiate radiation we don't have a
> specific bandwidth restriction. Are you aware of any country
> restricting any 5 GHz world roaming frequency (non DFS) or channel
> 1-11 on 2.4 GHz in terms of bandwidth used?
This is world roaming, so we never use any of the 5 GHz channels unless
we've heard a beacon. If we hear beacons on consecutive (non-DFS)
channels (say 36,40,44,48) we would even enable them and then allow
using 80 MHz there. We could try to prevent this in some way I guess,
but it'd be more complex, and I'm not sure it's needed. However, I think
we need to be able to use 80 MHz in world roaming situations, which the
bandwidth setting currently prevents.
johannes
next prev parent reply other threads:[~2012-12-13 22:32 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-06 16:53 [RFC 0/2] VHT regulatory Johannes Berg
2012-12-06 16:53 ` [RFC 1/2] regulatory: allow arbitrary channel widths Johannes Berg
2012-12-13 22:27 ` Luis R. Rodriguez
2012-12-13 22:28 ` Luis R. Rodriguez
2012-12-13 22:33 ` Johannes Berg [this message]
2012-12-13 22:33 ` Johannes Berg
2012-12-06 16:53 ` [RFC 2/2] cfg80211: check (VHT) bandwidth against regulatory Johannes Berg
2012-12-10 17:06 ` Johannes Berg
2012-12-13 22:34 ` Luis R. Rodriguez
2012-12-13 22:46 ` Johannes Berg
2012-12-13 23:12 ` Johannes Berg
2012-12-13 23:14 ` Johannes Berg
2012-12-13 22:38 ` Luis R. Rodriguez
2012-12-13 22:47 ` Johannes Berg
2012-12-13 22:49 ` Luis R. Rodriguez
2012-12-13 23:13 ` Bitterli, Felix
2012-12-13 23:16 ` Johannes Berg
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=1355437992.9463.30.camel@jlt4.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=green@qca.qualcomm.com \
--cc=linux-wireless@vger.kernel.org \
--cc=mcgrof@do-not-panic.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).