From: "John W. Linville" <linville@tuxdriver.com>
To: Michael Harris <harmic@gmail.com>
Cc: linux-wireless@vger.kernel.org, wireless-regdb@lists.infradead.org
Subject: Re: [wireless-regdb] [PATCH 1/1] wireless-regdb: Update rules for Australia (AU) to align with class licence
Date: Mon, 27 Oct 2014 13:31:41 -0400 [thread overview]
Message-ID: <20141027173141.GB28300@tuxdriver.com> (raw)
In-Reply-To: <1413111411-29509-1-git-send-email-harmic@gmail.com>
I'm always a bit cautious about merging regdb patches that loosen
the rules. Would anyone with more expertise on such regulations care
to comment on this one?
On Sun, Oct 12, 2014 at 09:56:51PM +1100, Michael Harris wrote:
> I am not sure where the existing regdb rules for Australia were derived from
> (perhaps some default template?) but they are a lot more restrictive than the
> actual class licence requirements.
>
> I have updated to the best of my ability according to the "Radiocommunications
> (Low Interference Potential Devices) Class Licence 2000" which can be found here:
>
> http://www.acma.gov.au/Industry/Spectrum/Radiocomms-licensing/Class-licences/class-licences
>
> There is also a useful FAQ for 2.4GHz WLANs here:
> http://www.acma.gov.au/Citizen/Consumer-info/My-connected-home/Wireless-local-area-networks/wireless-lans-in-the-24-ghz-band-faqs
>
> Signed-off-by: Michael Harris <harmic@gmail.com>
> ---
> db.txt | 20 +++++++++++++++-----
> 1 file changed, 15 insertions(+), 5 deletions(-)
>
> diff --git a/db.txt b/db.txt
> index f0e4312..94c7010 100644
> --- a/db.txt
> +++ b/db.txt
> @@ -78,12 +78,22 @@ country AT: DFS-ETSI
> # 60 gHz band channels 1-4, ref: Etsi En 302 567
> (57240 - 65880 @ 2160), (40), NO-OUTDOOR
>
> +# Reference: Radiocommunications (Low Interference Potential Devices) Class Licence 2000
> +# http://www.acma.gov.au/Industry/Spectrum/Radiocomms-licensing/Class-licences/class-licences
> country AU:
> - (2402 - 2482 @ 40), (20)
> - (5170 - 5250 @ 80), (17)
> - (5250 - 5330 @ 80), (24), DFS
> - (5490 - 5710 @ 80), (24), DFS
> - (5735 - 5835 @ 80), (30)
> + # Item 45A
> + (2400 - 2483 @ 40), (36)
> + # Item 44
> + (5150 - 5250 @ 80), (23), NO-OUTDOOR
> + # Item 44A (assuminging no TPC implemented).
> + # If TPC implemented then 23dBm allowed.
> + (5250 - 5350 @ 80), (20), NO-OUTDOOR, DFS
> + # Item 46 (assuming no TPC implemented)
> + # If TPC implemented then 30dBm allowed
> + (5470 - 5600 @ 80), (27), DFS
> + (5650 - 5725 @ 40), (27), DFS
> + # Item 45B
> + (5725 - 5850 @ 80), (36)
>
> country AW: DFS-ETSI
> (2402 - 2482 @ 40), (20)
> --
> 1.8.3.1
>
>
--
John W. Linville Someday the world will need a hero, and you
linville@tuxdriver.com might be all we have. Be ready.
_______________________________________________
wireless-regdb mailing list
wireless-regdb@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/wireless-regdb
next parent reply other threads:[~2014-10-27 17:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1413111411-29509-1-git-send-email-harmic@gmail.com>
2014-10-27 17:31 ` John W. Linville [this message]
2014-11-02 22:38 ` [wireless-regdb] [PATCH 1/1] wireless-regdb: Update rules for Australia (AU) to align with class licence Michael Harris
2014-10-23 6:45 Michael Harris
2014-11-07 20:59 ` John W. Linville
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=20141027173141.GB28300@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=harmic@gmail.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