Linux wireless drivers development
 help / color / mirror / Atom feed
From: "Johannes Berg" <johannes@sipsolutions.net>
To: "Luis R. Rodriguez" <lrodriguez@atheros.com>
Cc: linville@tuxdriver.com,
	"Luis R. Rodriguez" <lrodriguez@atheros.com>,
	linux-wireless@vger.kernel.org
Subject: Re: [PATCH 6/6] cfg80211: enable 5 GHz band for world regulatory domain
Date: Thu, 30 Oct 2008 10:24:17 +0100 (CET)	[thread overview]
Message-ID: <53ad401862d734b26836f0706a394525.squirrel@secure.sipsolutions.net> (raw)
In-Reply-To: <1225329594-21704-7-git-send-email-lrodriguez@atheros.com>

Luis R. Rodriguez wrote:
> Technically speaking since some countries do not support
> some channels in 5 GHz the world regulatory domain should not
> use them however APs should *not* be shipped in those countries
> which don't allow 5 GHz operation. Because of this we can
> safely assume we operate correctly in STA mode by forcing
> passive scan and disabling ad-hoc in 5 GHz. We leave out
> all DFS channels as we don't support DFS yet.

No,  this is incorrect. The linux kernel can well act as an AP.

> Signed-off-by: Luis R. Rodriguez <lrodriguez@atheros.com>
> ---
>  net/wireless/reg.c |   12 +++++++++++-
>  1 files changed, 11 insertions(+), 1 deletions(-)
>
> diff --git a/net/wireless/reg.c b/net/wireless/reg.c
> index dd1020b..ce0c730 100644
> --- a/net/wireless/reg.c
> +++ b/net/wireless/reg.c
> @@ -85,7 +85,11 @@ static u32 supported_bandwidths[] = {
>   * information to give us an alpha2 */
>  static const struct ieee80211_regdomain *cfg80211_regdomain;
>
> -/* We keep a static world regulatory domain in case of the absence of
> CRDA */
> +/* We keep a static world regulatory domain in case of the absence of
> CRDA.
> + * Although some countries disable 5 GHz completely it is up to the APs
> + * sold in those countries to not beacon, we can safely passive scan
> though
> + * on non DFS channels. We don't support yet DFS so don't include DFS
> + * channels yet (5260 MHz - 5700 MHz) */
>  static const struct ieee80211_regdomain world_regdom = {
>  	.n_reg_rules = 1,
>  	.alpha2 =  "00",
> @@ -93,6 +97,12 @@ static const struct ieee80211_regdomain world_regdom =
> {
>  		REG_RULE(2412-10, 2462+10, 40, 6, 20,
>  			NL80211_RRF_PASSIVE_SCAN |
>  			NL80211_RRF_NO_IBSS),
> +		REG_RULE(5170, 5260, 40, 6, 20,
> +			NL80211_RRF_PASSIVE_SCAN |
> +			NL80211_RRF_NO_IBSS),
> +		REG_RULE(5700, 5835, 40, 6, 20,
> +			NL80211_RRF_PASSIVE_SCAN |
> +			NL80211_RRF_NO_IBSS),
>  	}
>  };
>
> --
> 1.5.6.3
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-wireless"
> in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>
>


  reply	other threads:[~2008-10-30  9:24 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-30  1:19 [PATCH 0/6] cfg80211: few regulatory updates Luis R. Rodriguez
2008-10-30  1:19 ` [PATCH 1/6] cfg80211: a reg rule is invalid if freq diff is 0 Luis R. Rodriguez
2008-10-30  1:19   ` [PATCH 2/6] cfg80211: Add regulatory domain intersection capability Luis R. Rodriguez
2008-10-30  1:19     ` [PATCH 3/6] cfg80211: make print_regdomain_info() static Luis R. Rodriguez
2008-10-30  1:19       ` [PATCH 4/6] cfg80211: make use of reg macros on REG_RULE Luis R. Rodriguez
2008-10-30  1:19         ` [PATCH 5/6] cfg80211: Add kdoc for struct regulatory_request Luis R. Rodriguez
2008-10-30  1:19           ` [PATCH 6/6] cfg80211: enable 5 GHz band for world regulatory domain Luis R. Rodriguez
2008-10-30  9:24             ` Johannes Berg [this message]
2008-10-30 16:09               ` Luis R. Rodriguez
2008-10-30 17:18                 ` Johannes Berg
2008-10-30 17:43                   ` Luis R. Rodriguez
2008-10-30 18:12                   ` Jouni Malinen
2008-10-30  9:22   ` [PATCH 1/6] cfg80211: a reg rule is invalid if freq diff is 0 Johannes Berg
2008-10-30 19:40     ` 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=53ad401862d734b26836f0706a394525.squirrel@secure.sipsolutions.net \
    --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