Linux wireless drivers development
 help / color / mirror / Atom feed
From: "Luis R. Rodriguez" <lrodriguez@atheros.com>
To: linville@tuxdriver.com
Cc: linux-wireless@vger.kernel.org, ath9k-devel@lists.ath9k.org,
	"Luis R. Rodriguez" <lrodriguez@atheros.com>,
	Michael Green <Michael.Green@atheros.com>,
	Senthil Balasubramanian <senthilkumar@atheros.com>,
	David Quan <David.Quan@atheros.com>
Subject: Re: [PATCH v2] wireless-regdb: update US rules for 5600 MHz - 5650 MHz
Date: Tue, 27 Oct 2009 09:22:07 -0700	[thread overview]
Message-ID: <43e72e890910270922g555981tfb0a9b471ccaa662@mail.gmail.com> (raw)
In-Reply-To: <1256660178-5863-1-git-send-email-lrodriguez@atheros.com>

On Tue, Oct 27, 2009 at 9:16 AM, Luis R. Rodriguez
<lrodriguez@atheros.com> wrote:
> The FCC is trying to assist airports that use Terminal Doppler
> Weather Radar (TDWR) systems in avoiding interference with
> some outdoor wireless systems operating in the 5.4 GHz
> (5470 MHz - 5725 MHz) band. One of the things they have decided
> on is to disallow operation on the 5600 MHz - 5650 MHz frequency
> range inclusive. What this means in practice is 5 GHz 802.11
> devices programmed to operate in the US will have these
> channels now disabled:
>
>  * 5600 MHz [120] (disabled)
>  * 5620 MHz [124] (disabled)
>  * 5640 MHz [128] (disabled)
>
> This is documented on the FCC Knowledge based Publication
> Number: 443999 [1]
>
> [1] https://fjallfoss.fcc.gov/oetcf/kdb/forms/FTSSearchResultPage.cfm?switch=P&id=41732

And actually -- on second though I'm reviewing if we can just use
NO-IBSS, PASSIVE-SCAN, DFS on this frequency range. So please hold on
this.

  Luis

      reply	other threads:[~2009-10-27 16:22 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-27 16:16 [PATCH v2] wireless-regdb: update US rules for 5600 MHz - 5650 MHz Luis R. Rodriguez
2009-10-27 16:22 ` Luis R. Rodriguez [this message]

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=43e72e890910270922g555981tfb0a9b471ccaa662@mail.gmail.com \
    --to=lrodriguez@atheros.com \
    --cc=David.Quan@atheros.com \
    --cc=Michael.Green@atheros.com \
    --cc=ath9k-devel@lists.ath9k.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=senthilkumar@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