From: "John W. Linville" <linville@tuxdriver.com>
To: Linux Wireless Stuff for IOPEN <linwir-list@iopen.net>
Cc: wireless-regdb@lists.infradead.org, linux-wireless@vger.kernel.org
Subject: Re: [wireless-regdb] Update regulatory rules for New Zealand (NZ)
Date: Tue, 7 Feb 2012 14:56:22 -0500 [thread overview]
Message-ID: <20120207195622.GH5560@tuxdriver.com> (raw)
In-Reply-To: <4E7AA97D.40402@iopen.net>
Sorry for the delay, and thanks for the patch.
Could you perhaps produce the patch in "diff -u" format? Also,
could you include a proper "Signed-off-by" line?
Thanks,
John
On Thu, Sep 22, 2011 at 03:20:29PM +1200, Linux Wireless Stuff for IOPEN wrote:
> On 09/20/2011 02:13 AM, John W. Linville wrote:
> > On Sat, Sep 17, 2011 at 01:12:26PM +1200, Linux Wireless Stuff for IOPEN wrote:
> >> From Fedora 14 :
> >> ==============
> >>
> >>> country NZ:
> >>> (2402 - 2482 @ 40), (N/A, 30)
> >>> (5170 - 5250 @ 20), (3, 23)
> >>> (5250 - 5330 @ 20), (3, 23), DFS
> >>> (5735 - 5835 @ 20), (3, 30)
> >>
> >> Updates for 2.4 GHz :
> >> ===================
> >>
> >> Frequency range is 2400 to 2483.5 (Ref 1)
> >> Maximum EIRP is 36 dBm (4 W) (Ref 1)
> >>
> >> Updates for 5 GHz :
> >> =================
> >>
> >> 5150 - 5250 23 dBm (200 mW) indoor only (Ref 1,3)
> >> 5250 - 5350 23 dBm (200 mW) indoor/outdoor,DFS+TPC (Ref 1,3)
> >> 5725 - 5875 36 dBm ( 4 W) PtMP/PtP (Ref 1,3)
> >> 5725 - 5825 53 dBm (200 W) PtP fixed (Ref 1,2,3)
> >>
> >> And possibly this via the Spread Spectrum Device provision
> >>
> >> 5470 - 5725 30 dBm ( 1 W) requires DFS+TPC (Ref 3)
> >>
> >> Maximum power density is specified for some chunks.
> >>
> >> References :
> >> ==========
> >> 1 :
> >>> http://www.rsm.govt.nz/cms/licensees/types-of-licence/general-user-licences/fixed-radio-link-devices/information-on-the-operation-of-wireless-lan-and-related-systems-in-the-2-ghz-and-5-ghz-bands
> >> 2 :
> >>> http://www.rsm.govt.nz/cms/licensees/types-of-licence/general-user-licences/fixed-radio-link-devices
> >> 3 :
> >>> http://www.rsm.govt.nz/cms/licensees/types-of-licence/general-user-licences/short-range-devices
> >>
> >> Cheers
> >> The IOPEN wireless deployers
> >
> > Thanks for the info. Any chance you could propose this in the form
> > of a patch?
>
> TaDa!
>
> kernel.org is still down so we've derived the below patch from ...
>
> > http://linuxwireless.org/download/wireless-regdb/wireless-regdb-2011.04.28.tar.bz2
>
> For the DFS items, if TPC isn't used the maximum power is 3 dB less, but
> there's no way of representing that in your scheme.
>
> -----CUT-----
> *** db.txt 2011-04-29 07:17:40.000000000 +1200
> --- db-updated.txt 2011-09-22 14:36:04.966154148 +1200
> ***************
>
> *** 512,521 ****
> (5735 - 5835 @ 40), (N/A, 30)
>
> country NZ:
> ! (2402 - 2482 @ 40), (N/A, 30)
> ! (5170 - 5250 @ 20), (3, 23)
> ! (5250 - 5330 @ 20), (3, 23), DFS
> ! (5735 - 5835 @ 20), (3, 30)
>
> country OM:
> (2402 - 2482 @ 40), (N/A, 20)
> --- 512,523 ----
> (5735 - 5835 @ 40), (N/A, 30)
>
> country NZ:
> ! (2400 - 2483 @ 40), (N/A, 36)
> ! (5150 - 5250 @ 40), (N/A, 23), NO-OUTDOOR
> ! (5250 - 5350 @ 40), (N/A, 23), DFS
> ! (5470 - 5725 @ 40), (N/A, 30), DFS
> ! (5725 - 5875 @ 40), (N/A, 36)
> ! (5725 - 5825 @ 40), (N/A, 53), PTP-ONLY
>
> country OM:
> (2402 - 2482 @ 40), (N/A, 20)
> -----CUT-----
>
> Cheers
> The IOPEN wireless deployers
>
--
John W. Linville Someday the world will need a hero, and you
linville@tuxdriver.com might be all we have. Be ready.
prev parent reply other threads:[~2012-02-07 20:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-17 1:12 Update regulatory rules for New Zealand (NZ) Linux Wireless Stuff for IOPEN
2011-09-19 14:13 ` John W. Linville
2011-09-22 3:20 ` [wireless-regdb] " Linux Wireless Stuff for IOPEN
2012-02-07 19:56 ` John W. Linville [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=20120207195622.GH5560@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linwir-list@iopen.net \
--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).