linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Seth Forshee <seth.forshee@canonical.com>
To: Wei Zhong <wzhong@google.com>
Cc: wireless-regdb@lists.infradead.org, linux-wireless@vger.kernel.org
Subject: Re: wireless-regdb: update CA rules for 5600 - 5650 mHz
Date: Thu, 2 Jul 2015 08:48:01 -0500	[thread overview]
Message-ID: <20150702134801.GA40677@ubuntu-hedt> (raw)
In-Reply-To: <CAHr=Vq=hJr6WUQgFXftMSG2zYgwtCXgoTaXBzRfM8-kQa2-K2w@mail.gmail.com>

On Wed, Jul 01, 2015 at 10:44:09PM -0700, Wei Zhong wrote:
> commit 2fef4cad8a1bd9cbbf178e59a1b3ca672b057095
> Author: Wei Zhong <wzhong@google.com>
> Date:   Wed Jul 1 22:39:09 2015 -0700
> 
>     wireless-regdb: update CA rules for 5600 - 5650 mHz
> 
>     Related regulation:
>     http://www.ic.gc.ca/eic/site/smt-gst.nsf/eng/sf10971.html#s6.2.3
> 
>     Frequency Bands 5470-5600 MHz and 5650-5725 MHz
>     Until further notice, devices subject to this section [i.e. Wifi device
>     supporting 5 GHz bands] shall not be capable of transmitting in the band
>     5600-5650 MHz. This restriction is for the protection of Environment
>     Canada’s weather radars operating in this band.

Thanks for the patch. There are a couple of issues though, plus a
question.

First, this project requires that you add a Signed-off-by tag to the
commit message to acknowledge your agreement to the Developer
Certificate of Origin. Please see the CONTRIBUTING file for more
information.

Second, the patch is not in the correct format. It looks like to me you
pasted the output from git-show, which resulted in mangled white space
and other issues. Please use git-format-patch to create the patch, then
send it using git-send-email or else send the patch as an attachment.

> diff --git a/db.txt b/db.txt
> index 809cd3c..da0cfad 100644
> --- a/db.txt
> +++ b/db.txt
> @@ -216,7 +216,8 @@ country CA: DFS-FCC
>         (2402 - 2472 @ 40), (30)
>         (5170 - 5250 @ 80), (17), AUTO-BW
>         (5250 - 5330 @ 80), (24), DFS, AUTO-BW
> -       (5490 - 5730 @ 160), (24), DFS
> +       (5490 - 5600 @ 80), (24), DFS
> +       (5650 - 5730 @ 40), (24), DFS

Why isn't 80MHz channel bandwidth allowed in the 5650-5730 range?

Thanks,
Seth

  reply	other threads:[~2015-07-02 13:48 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-02  5:44 wireless-regdb: update CA rules for 5600 - 5650 mHz Wei Zhong
2015-07-02 13:48 ` Seth Forshee [this message]
2015-07-02 14:21   ` Wei Zhong
2015-07-02 14:31     ` Seth Forshee
2015-07-03 11:08 ` Zefir Kurtisi
2015-07-03 14:20   ` Wei Zhong
2015-07-03 15:01     ` Zefir Kurtisi
2015-07-06 13:27       ` Seth Forshee
2015-07-06 14:40         ` Zefir Kurtisi
2015-07-06 17:13           ` Wei Zhong
2015-07-07 20:11           ` Seth Forshee
2015-07-08 10:19             ` Zefir Kurtisi
2015-07-09 14:04               ` Seth Forshee

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=20150702134801.GA40677@ubuntu-hedt \
    --to=seth.forshee@canonical.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=wireless-regdb@lists.infradead.org \
    --cc=wzhong@google.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).