linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Krishna Chaitanya <chaitanya.mgit@gmail.com>
To: Seth Forshee <seth.forshee@canonical.com>
Cc: wireless-regdb@lists.infradead.org,
	linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH] wireless-regdb: update 60ghz band rules for us
Date: Wed, 16 Jan 2019 14:09:05 +0530	[thread overview]
Message-ID: <CABPxzYK+Tu678C=84i3+67gA1EBw_pG3cJ1y1ZvWZobU6iS8Dg@mail.gmail.com> (raw)
In-Reply-To: <20181218080815.19395-1-chaitanya.mgit@gmail.com>

On Tue, Dec 18, 2018 at 1:38 PM <chaitanya.mgit@gmail.com> wrote:
>
> From: Chaitanya Tata <Chaitanya.Mgit@gmail.com>
>
> Include channels 4, 5 & 6 for US in 60GHz band. FCC extended the
> 57-64GHz band till 71GHz with almost same rules.
> ---
>  db.txt | 6 +++---
>  1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/db.txt b/db.txt
> index fa5c0e0..ae650dd 100644
> --- a/db.txt
> +++ b/db.txt
> @@ -1280,9 +1280,9 @@ country US: DFS-FCC
>         (5490 - 5730 @ 160), (23), DFS
>         (5735 - 5835 @ 80), (30)
>         # 60g band
> -       # reference: http://cfr.regstoday.com/47cfr15.aspx#47_CFR_15p255
> -       # channels 1,2,3, EIRP=40dBm(43dBm peak)
> -       (57240 - 63720 @ 2160), (40)
> +       # reference: section IV-D https://docs.fcc.gov/public/attachments/FCC-16-89A1.pdf
> +       # channels 1-6 EIRP=40dBm(43dBm peak)
> +       (57240 - 71000 @ 2160), (40)
>
>  country UY: DFS-FCC
>         (2402 - 2482 @ 40), (20)
>
Kalle/Seth,

Any update on this? Patchwork shows its delegated to you(may be by default).

  reply	other threads:[~2019-01-16  8:39 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-18  8:08 [PATCH] wireless-regdb: update 60ghz band rules for us chaitanya.mgit
2019-01-16  8:39 ` Krishna Chaitanya [this message]
2019-01-17  6:50   ` Kalle Valo
2019-01-17 19:47     ` Krishna Chaitanya
2019-01-22 20:23       ` Seth Forshee
2019-01-22 21:13 ` Seth Forshee
2019-01-23 10:49   ` Krishna Chaitanya
2019-02-17 10:53     ` 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='CABPxzYK+Tu678C=84i3+67gA1EBw_pG3cJ1y1ZvWZobU6iS8Dg@mail.gmail.com' \
    --to=chaitanya.mgit@gmail.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=seth.forshee@canonical.com \
    --cc=wireless-regdb@lists.infradead.org \
    /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).