public inbox for wireless-regdb@lists.infradead.org
 help / color / mirror / Atom feed
From: Seth Forshee <sforshee@kernel.org>
To: CaffeeLake <pascalcoffeelake@gmail.com>
Cc: wireless-regdb@lists.infradead.org, linux-wireless@vger.kernel.org
Subject: Re: [wireless-regdb] wireless-regdb: Update regulatory rules for Japan (JP) on 6GHz
Date: Wed, 9 Nov 2022 10:27:13 -0600	[thread overview]
Message-ID: <Y2vU4YAs5wmibcGF@ubuntu-x1> (raw)
In-Reply-To: <20221030110510.752996-1-PascalCoffeeLake@gmail.com>

On Sun, Oct 30, 2022 at 08:05:10PM +0900, CaffeeLake wrote:
> Support 6GHz for JP Region.
> 
> The Ministry of Internal Affairs and Communications has approved 6GHz (5925 - 6425 MHz) in Japan.
> 
> Source: https://www.soumu.go.jp/main_content/000833682.pdf
> 
> Signed-off-by: CaffeeLake <PascalCoffeeLake@gmail.com>

Sorry for the slow response on your patches.

This patch conflicts with the other patch you sent for 5 GHz. I can
easily reconcile the conflict in the rules, but I cannot read the linked
documents (and machine translations is not proving very helpful). I
can't tell if the link in this patch supersedes the link from the other
patch, or if they are complimentary and should both be kept in the
database. Can you clarify, or else resend both as a series with the
second patch based off of the modifications from the first?

Thanks,
Seth

> ---
>  db.txt | 3 +++
>  1 file changed, 3 insertions(+)
> 
> diff --git a/db.txt b/db.txt
> index 012824f..96527c9 100644
> --- a/db.txt
> +++ b/db.txt
> @@ -907,6 +907,8 @@ country JO: DFS-JP
>  	(5170 - 5250 @ 80), (23)
>  	(5735 - 5835 @ 80), (23)
> 
> +# Source:
> +# https://www.soumu.go.jp/main_content/000833682.pdf
>  country JP: DFS-JP
>  	(2402 - 2482 @ 40), (20)
>  	(2474 - 2494 @ 20), (20), NO-OFDM
> @@ -914,6 +916,7 @@ country JP: DFS-JP
>  	(5170 - 5250 @ 80), (20), AUTO-BW
>  	(5250 - 5330 @ 80), (20), DFS, AUTO-BW
>  	(5490 - 5710 @ 160), (23), DFS
> +	(5925 - 6425 @ 160), (200 mW), NO-OUTDOOR
>  	# 60 GHz band channels 2-4 at 10mW,
>  	# ref: http://www.arib.or.jp/english/html/overview/doc/1-STD-T74v1_1.pdf
>  	(57000 - 66000 @ 2160), (10 mW)
> --
> 2.37.3
> 

_______________________________________________
wireless-regdb mailing list
wireless-regdb@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/wireless-regdb


  reply	other threads:[~2022-11-09 16:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-30 11:05 [wireless-regdb] wireless-regdb: Update regulatory rules for Japan (JP) on 6GHz CaffeeLake
2022-11-09 16:27 ` Seth Forshee [this message]
2022-12-05 22:09 ` 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=Y2vU4YAs5wmibcGF@ubuntu-x1 \
    --to=sforshee@kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=pascalcoffeelake@gmail.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