From: "Luis R. Rodriguez" <mcgrof@do-not-panic.com>
To: linville@tuxdriver.com
Cc: linux-wireless@vger.kernel.org,
wireless-regdb@lists.infradead.org,
"Luis R. Rodriguez" <mcgrof@do-not-panic.com>
Subject: [PATCH 08/23] wireless-regdb: update OM's 5 GHz rules
Date: Fri, 1 Nov 2013 15:03:03 +0100 [thread overview]
Message-ID: <1383314598-21240-9-git-send-email-mcgrof@do-not-panic.com> (raw)
In-Reply-To: <1383314598-21240-1-git-send-email-mcgrof@do-not-panic.com>
This:
o removes the last 5 GHz frequency range
o increases the max EIRP on the first 5 GHz
frequency range from 17 dBm to 20 dBm
o enables VHT80 for all 5 GHz frequency ranges
Source is QCA's regulatory team's efforts.
Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com>
---
db.txt | 7 +++----
1 file changed, 3 insertions(+), 4 deletions(-)
diff --git a/db.txt b/db.txt
index e2740a6..8366b3b 100644
--- a/db.txt
+++ b/db.txt
@@ -602,10 +602,9 @@ country NZ: DFS-FCC
country OM: DFS-ETSI
(2402 - 2482 @ 40), (20)
- (5170 - 5250 @ 40), (17)
- (5250 - 5330 @ 40), (20), DFS
- (5490 - 5710 @ 40), (20), DFS
- (5735 - 5835 @ 40), (30)
+ (5170 - 5250 @ 80), (20)
+ (5250 - 5330 @ 80), (20), DFS
+ (5490 - 5710 @ 80), (27), DFS
country PA: DFS-FCC
(2402 - 2472 @ 40), (27)
--
1.8.4.rc3
next prev parent reply other threads:[~2013-11-01 14:03 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-01 14:02 [PATCH 00/23] wireless-regdb: general rules updates Luis R. Rodriguez
2013-11-01 14:02 ` [PATCH 01/23] wireless-regdb: update BN's 5 GHz rules Luis R. Rodriguez
2013-11-01 14:02 ` [PATCH 02/23] wireless-regdb: update CA's " Luis R. Rodriguez
2013-11-01 14:02 ` [PATCH 03/23] wireless-regdb: update KE's " Luis R. Rodriguez
2013-11-01 14:02 ` [PATCH 04/23] wireless-regdb: update KP's " Luis R. Rodriguez
2013-11-01 14:03 ` [PATCH 05/23] wireless-regdb: update MC's " Luis R. Rodriguez
2013-11-01 14:03 ` [PATCH 06/23] wireless-regdb: update MA's " Luis R. Rodriguez
2013-11-01 14:03 ` [PATCH 07/23] wireless-regdb: update NP's " Luis R. Rodriguez
2013-11-01 14:03 ` Luis R. Rodriguez [this message]
2013-11-01 14:03 ` [PATCH 09/23] wireless-regdb: update PG's " Luis R. Rodriguez
2013-11-01 14:03 ` [PATCH 10/23] wireless-regdb: update RU's " Luis R. Rodriguez
2013-11-01 14:03 ` [PATCH 11/23] wireless-regdb: update RW's " Luis R. Rodriguez
2013-11-01 14:03 ` [PATCH 12/23] wireless-regdb: update SA's " Luis R. Rodriguez
2013-11-01 14:03 ` [PATCH 13/23] wireless-regdb: update TT's " Luis R. Rodriguez
2013-11-01 14:03 ` [PATCH 14/23] wireless-regdb: update ZA's " Luis R. Rodriguez
2013-11-01 14:03 ` [PATCH 15/23] wireless-regdb: update BG's regulatory rules Luis R. Rodriguez
2013-11-01 14:03 ` [PATCH 16/23] wireless-regdb: update CO's " Luis R. Rodriguez
2013-11-01 14:03 ` [PATCH 17/23] wireless-regdb: update GE's " Luis R. Rodriguez
2013-11-01 14:03 ` [PATCH 18/23] wireless-regdb: update PR's " Luis R. Rodriguez
2013-11-01 14:03 ` [PATCH 19/23] wireless-regdb: update KR's " Luis R. Rodriguez
2013-11-01 14:03 ` [PATCH 20/23] wireless-regdb: update MX's " Luis R. Rodriguez
2013-11-01 14:03 ` [PATCH 21/23] wireless-regdb: update PA's " Luis R. Rodriguez
2013-11-01 14:03 ` [PATCH 22/23] wireless-regdb: update TW's " Luis R. Rodriguez
2013-11-01 14:03 ` [PATCH 23/23] wireless-regdb: update US' " Luis R. Rodriguez
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=1383314598-21240-9-git-send-email-mcgrof@do-not-panic.com \
--to=mcgrof@do-not-panic.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.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).