linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Chen-Yu Tsai <wens@kernel.org>
To: Richard Huynh <voxlympha@gmail.com>
Cc: linux-wireless@vger.kernel.org, wireless-regdb@lists.infradead.org
Subject: Re: [PATCH] wireless-regdb: Update regulatory info for Australia (AU) for 2025
Date: Wed, 8 Oct 2025 16:42:43 +0800	[thread overview]
Message-ID: <CAGb2v67RvP5ykKJR1yOpZ9y2b=dAA3mkXFUn8a7U_pNmudS37A@mail.gmail.com> (raw)
In-Reply-To: <20251007230450.69998-1-voxlympha@gmail.com>

On Wed, Oct 8, 2025 at 7:05 AM Richard Huynh <voxlympha@gmail.com> wrote:
>
> As of October 1 2025, a new class licence is in effect[1]
> Update the link and references in the comments to it
>
> Additionally for the lower part of 6Ghz spectrum:
> - Allow for EHT-320 as it complies with PSD limits
> - Expand the upper range up to 6585 as permitted in new licence
>
> [1] https://www.legislation.gov.au/Details/F2025L01047
>
> Signed-off-by: Richard Huynh <voxlympha@gmail.com>
> ---
>  db.txt | 25 +++++++++++++------------
>  1 file changed, 13 insertions(+), 12 deletions(-)
>
> diff --git a/db.txt b/db.txt
> index 16bcb32..93d709e 100644
> --- a/db.txt
> +++ b/db.txt
> @@ -145,43 +145,44 @@ country AT: DFS-ETSI
>
>  # Source:
>  # 'Item' in the comments below refers to each numbered rule found at:
> -# https://www.legislation.gov.au/Details/F2023C00524
> +# https://www.legislation.gov.au/Details/F2025L01047 within Table 8
> +# except for 5850-5875 which is found in Table 1.
>  # Both DFS-ETSI and DFS-FCC are acceptable per AS/NZS 4268 Appendix B.
>  # The EIRP for DFS bands can be increased by 3dB if TPC is implemented.
>  # In order to allow 80MHz operation between 5650-5730MHz the upper boundary
>  # of this more restrictive band has been shifted up by 5MHz from 5725MHz.
>  country AU: DFS-ETSI
> -       # Item 58
> +       # Item 1
>         (915 - 920 @ 4), (1000 mW)
>         (920 - 928 @ 8), (1000 mW)

Side note, I think this should be just one band. We don't artificially
split bands on channel boundaries. If you could, please send another
patch to merge them.

> -       # Item 59
> +       # Item 3

Items 3 and 7? I can fix this when applying the patch.

>         (2400 - 2483.5 @ 40), (4000 mW)
>
> -       # Item 61
> +       # Item 10
>         (5150 - 5250 @ 80), (200 mW), NO-OUTDOOR, AUTO-BW
>
> -       # Item 62 (200 mW allowed if TPC is used)
> +       # Item 11 (200 mW allowed if TPC is used)
>         (5250 - 5350 @ 80), (100 mW), NO-OUTDOOR, AUTO-BW, DFS
>
> -       # Item 63(a) (1000 mW with TPC)
> +       # Item 12(a) (1000 mW with TPC)
>         (5470 - 5600 @ 80), (500 mW), DFS
>
> -       # Item 63(b) (1000 mW with TPC)
> +       # Item 12(b) (1000 mW with TPC)
>         # The end is 5725 but we borrow 5 MHz from the following less restrictive band
>         # so we can get an 80 MHz channel.
>         (5650 - 5730 @ 80), (500 mW), DFS
>
> -       # Item 60
> +       # Item 9
>         (5730 - 5850 @ 80), (4000 mW), AUTO-BW
>
> -       # Item 22
> +       # Item 22 of Table 1
>         (5850 - 5875 @ 20), (25 mW), AUTO-BW
>
> -       # Item 63AA (25 mW if outdoors)
> -       (5925 - 6425 @ 160), (250 mW), NO-OUTDOOR
> +       # Item 13 (25 mW if outdoors)
> +       (5925 - 6585 @ 320), (250 mW), NO-OUTDOOR
>
> -       # Item 65
> +       # Item 18
>         (57000 - 71000 @ 2160), (20000 mW), NO-OUTDOOR

The rest look correct.

Thanks
ChenYu

>  country AW: DFS-ETSI
> --
> 2.51.0
>
>

      reply	other threads:[~2025-10-08  8:42 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-07 23:04 [PATCH] wireless-regdb: Update regulatory info for Australia (AU) for 2025 Richard Huynh
2025-10-08  8:42 ` Chen-Yu Tsai [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='CAGb2v67RvP5ykKJR1yOpZ9y2b=dAA3mkXFUn8a7U_pNmudS37A@mail.gmail.com' \
    --to=wens@kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=voxlympha@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;
as well as URLs for NNTP newsgroup(s).