From: "seth.forshee" <seth.forshee@canonical.com>
To: "junping.xu@jaguarwave.com" <junping.xu@jaguarwave.com>
Cc: wireless-regdb <wireless-regdb@lists.infradead.org>,
linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: wireless-regdb: Please update regulatory rules for Japan (JP) on 60GHz
Date: Mon, 8 Apr 2019 07:48:29 -0500 [thread overview]
Message-ID: <20190408124829.GD15126@ubuntu-xps13> (raw)
In-Reply-To: <2019040118074276659215@jaguarwave.com>
On Mon, Apr 01, 2019 at 06:07:44PM +0800, junping.xu@jaguarwave.com wrote:
> Hi Forsheee,
> The 60GHz band defined for Japan was between 59-66GHz, but is has been Updated to support 57-66Ghz about 2 years ago。
> However, the latest wireless-regdb still containning the original regulatory information as below. Please help to check the infomation
> and update the regulatory.bin.
>
> db.txt:
> ......
> country JP: DFS-JP
> (2402 - 2482 @ 40), (20)
> (2474 - 2494 @ 20), (20), NO-OFDM
> (4910 - 4990 @ 40), (23)
> (5030 - 5090 @ 40), (23)
> (5170 - 5250 @ 80), (20), AUTO-BW
> (5250 - 5330 @ 80), (20), DFS, AUTO-BW
> (5490 - 5710 @ 160), (23), DFS
> # 60 GHz band channels 2-4 at 10mW,
> # ref: http://www.arib.or.jp/english/html/overview/doc/1-STD-T74v1_1.pdf
The only change which is required to change:
> (59000 - 66000 @ 2160), (10 mW)
to:
(57000 - 66000 @ 2160), (10 mW)
Is that right? Can you provide a link to the documentation which
supports this change? The current link above this rule appears to be
broken.
Thanks,
Seth
next parent reply other threads:[~2019-04-08 12:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <2019040118074276659215@jaguarwave.com>
2019-04-08 12:48 ` seth.forshee [this message]
2019-04-25 22:00 ` [wireless-regdb] wireless-regdb: Please update regulatory rules for Japan (JP) on 60GHz b.K.il.h.u+tigbuh
2019-04-25 22:01 ` b.K.il.h.u+tigbuh
2019-05-15 13:15 ` 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=20190408124829.GD15126@ubuntu-xps13 \
--to=seth.forshee@canonical.com \
--cc=junping.xu@jaguarwave.com \
--cc=linux-wireless@vger.kernel.org \
--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