From: Seth Forshee <seth.forshee@canonical.com>
To: Chen-Yu Tsai <wens@csie.org>
Cc: wireless-regdb@lists.infradead.org, linux-wireless@vger.kernel.org
Subject: Re: [PATCH v2 3/5] wireless-regdb: Add U-NII-1 (5150 ~ 5250 MHz) band for Taiwan (TW)
Date: Mon, 3 Aug 2015 13:40:15 -0500 [thread overview]
Message-ID: <20150803184015.GE21180@ubuntu-hedt> (raw)
In-Reply-To: <1437622380-4154-4-git-send-email-wens@csie.org>
On Thu, Jul 23, 2015 at 11:32:58AM +0800, Chen-Yu Tsai wrote:
> Taiwan's Ministry of Transportation and Communications revised its
> frequency allocation rules [1] on 2014/11/17, opening up 5150 ~ 5250
> MHz to U-NII applications.
>
> Taiwan's regulatory body, NCC, officially stated [3][4] that until
> the technical regulatory standard [2] are updated to cover this part
> of the spectrum, FCC rules (part 15E, 15.407, effective 2014/06/02)
> shall serve in its place.
>
> Also add AUTO-BW to this and the next (5250 ~ 5350 MHz) rule, so the
> system can actually use VHT160 channels spanning these two rules.
>
> [1] http://www.motc.gov.tw/websitedowndoc?file=post/201411171137330.doc&filedisplay=Table+of+radio+frequency+allocation.doc
> [2] http://www.ncc.gov.tw/english/show_file.aspx?table_name=news&file_sn=681
> [3] http://www.rheintech.com/our-blog/item/585-taiwan-ncc-opens-5150-5250-mhz-for-wireless-devices
> [4] Proposal #10312260 (p.6, Chinese),
> http://www.etc.org.tw/_library/K00/%E9%9B%BB%E4%BF%A1%E7%B5%82%E7%AB%AF%E8%A8%AD%E5%82%99%E5%AF%A9%E9%A9%97/1031223_nccqa56.pdf
>
> Signed-off-by: Chen-Yu Tsai <wens@csie.org>
> ---
> db.txt | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/db.txt b/db.txt
> index 8a05c57..cadd52c 100644
> --- a/db.txt
> +++ b/db.txt
> @@ -1127,7 +1127,8 @@ country TT: DFS-FCC
> # (section 3.10.1, 4.7)
> country TW: DFS-JP
> (2400 - 2483.5 @ 40), (30)
> - (5250 - 5350 @ 80), (17), DFS
> + (5150 - 5250 @ 80), (30), AUTO-BW
> + (5250 - 5350 @ 80), (17), DFS, AUTO-BW
It would really make more sense for an update to the US power limit in
5150-5250 to precede this one if you're using the US rules as the
justification for the power limit here. Going through these patches in
order, I was initially confused here why it didn't match the US rule
until I looked at the next patch.
But, as I mentioned in the reply to that patch, I think the change to
the US power limit is incorrect, thus this one would be incorrect as
well.
next prev parent reply other threads:[~2015-08-03 18:40 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-23 3:32 [PATCH v2 0/5] wireless-regdb: Update TW and US rules to latest regulations Chen-Yu Tsai
2015-07-23 3:32 ` [PATCH v2 1/5] wireless-regdb: Update U-NII-2c (5470 ~ 5725 MHz) rules for Taiwan (TW) Chen-Yu Tsai
2015-08-03 18:27 ` Seth Forshee
2015-08-04 1:26 ` Chen-Yu Tsai
2015-08-04 1:55 ` Chen-Yu Tsai
2015-08-04 13:37 ` Seth Forshee
2015-07-23 3:32 ` [PATCH v2 2/5] wireless-regdb: Update regulatory rule boundary frequencies " Chen-Yu Tsai
2015-07-23 3:32 ` [PATCH v2 3/5] wireless-regdb: Add U-NII-1 (5150 ~ 5250 MHz) band " Chen-Yu Tsai
2015-08-03 18:40 ` Seth Forshee [this message]
2015-07-23 3:32 ` [PATCH v2 4/5] wireless-regdb: Update 5GHz rules for US Chen-Yu Tsai
2015-08-03 18:34 ` Seth Forshee
2015-08-03 18:47 ` Seth Forshee
2015-08-04 1:31 ` Chen-Yu Tsai
2015-08-04 13:43 ` Seth Forshee
2015-07-23 3:33 ` [PATCH v2 5/5] wireless-regdb: Update 5 GHz rules for Taiwan (TW) to follow US Chen-Yu Tsai
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=20150803184015.GE21180@ubuntu-hedt \
--to=seth.forshee@canonical.com \
--cc=linux-wireless@vger.kernel.org \
--cc=wens@csie.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;
as well as URLs for NNTP newsgroup(s).