public inbox for wireless-regdb@lists.infradead.org
 help / color / mirror / Atom feed
From: sforshee <sforshee@kernel.org>
To: kleo <kleo@hak.dog>
Cc: wireless-regdb <wireless-regdb@lists.infradead.org>,
	linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: [wireless-regdb] wireless-regdb: Update regulatory rules for Philippines (PH)
Date: Fri, 23 Dec 2022 10:03:56 -0600	[thread overview]
Message-ID: <Y6XRbJThM4oKMOVY@ubuntu-x1> (raw)
In-Reply-To: <184ec3a63fe.d96b82f6427171.7593361304891506395@hak.dog>

Sorry for the slow response. Please see my responses below.

In addition to those comments, the patch isn't formatted correctly for
application, and it is missing a Signed-off-by tag as noted in the
CONTRIBUTING file. For sending your patch I suggest using 'git
format-patch' to export the patch to a file and then either using 'git
send-email' to send it as an email or attaching the patch to your email
message.

On Wed, Dec 07, 2022 at 06:56:00PM +0800, kleo wrote:
> diff --git a/db.txt b/db.txt
> index 3f74194..fa9ffd7 100644
> --- a/db.txt
> +++ b/db.txt
> @@ -1368,11 +1368,17 @@ country PG: DFS-FCC
>         (5735 - 5835 @ 80), (30)
>  
>  country PH: DFS-FCC
> -       (2402 - 2482 @ 40), (20)
> -       (5170 - 5250 @ 80), (17), AUTO-BW
> -       (5250 - 5330 @ 80), (24), DFS, AUTO-BW
> -       (5490 - 5730 @ 160), (24), DFS
> -       (5735 - 5835 @ 80), (30)
> +       # https://ntc.gov.ph/wp-content/uploads/2015/10/LawsRulesRegulations/MemoCirculars/MC2003/MC-09-09-2003.pdf
> +       # https://ntc.gov.ph/wp-content/uploads/2015/10/LawsRulesRegulations/MemoCirculars/MC2013/MC-03-08-2013.pdf
> +       # https://ntc.gov.ph/wp-content/uploads/2016/MC/Explanatory-MC-No-01-01-2016.pdf
> +       # https://ntc.gov.ph/wp-content/uploads/2022/mc/Memorandum_Cicurlar_No._002-09-2021.pdf

The documents you linked to establish use of the frequency bands but
don't seem to contain any information about the relevant power limits
and other requirements. Where did this information come from?

> +       (915 - 918 @ 2), (30)

I don't see anything in the above documents about the 915-918 MHz band.
I also don't see that range listed in this table of frequency
allocations that I found:

https://ntc.gov.ph/wp-content/uploads/2022/frequencyallocations/NRFAT_Rev_2020.pdf

What's the basis for allowing this range?

Thanks,
Seth

> +       (2400 - 2483.5 @ 40), (24)
> +       (5150 - 5250 @ 80), (24), AUTO-BW
> +       (5250 - 5350 @ 80), (24), DFS, AUTO-BW
> +       (5470 - 5730 @ 160), (24), DFS
> +       (5730 - 5850 @ 80), (30)
> +       (57000 - 66000 @ 2160), (40)
>  
>  country PK: DFS-JP
>         # https://fab.gov.pk/type-approval/
> 
> c5da72a2fef48891aceb3f3378afbb12a2778c83e9f053f5d23e589630536b61  country-ph.patch
> 
> kleo
> 
> 
> 



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

      reply	other threads:[~2022-12-23 16:04 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-07 10:56 [wireless-regdb] wireless-regdb: Update regulatory rules for Philippines (PH) kleo
2022-12-23 16:03 ` sforshee [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=Y6XRbJThM4oKMOVY@ubuntu-x1 \
    --to=sforshee@kernel.org \
    --cc=kleo@hak.dog \
    --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