diff mbox series

[v2] wireless-regdb: Update regulatory rules for South Korea

Message ID 1556314283-17842-1-git-send-email-peter.oh@bowerswilkins.com (mailing list archive)
State Not Applicable
Delegated to: Johannes Berg
Headers show
Series [v2] wireless-regdb: Update regulatory rules for South Korea | expand

Commit Message

Peter Oh April 26, 2019, 9:31 p.m. UTC
From: Peter Oh <peter.oh@bowerswilkins.com>

Update power limit as documented in:
http://www.law.go.kr/%ED%96%89%EC%A0%95%EA%B7%9C%EC%B9%99/
%EC%8B%A0%EA%B3%A0%ED%95%98%EC%A7%80%EC%95%84%EB%8B%88%ED
%95%98%EA%B3%A0%EA%B0%9C%EC%84%A4%ED%95%A0%EC%88%98%EC%9E
%88%EB%8A%94%EB%AC%B4%EC%84%A0%EA%B5%AD%EC%9A%A9%EB%AC%B4
%EC%84%A0%EA%B8%B0%EA%B8%B0/(2018-89,20181227)
which revised on December 27, 2018.

Signed-off-by: Peter Oh <peter.oh@bowerswilkins.com>
---
 db.txt | 11 ++++++-----
 1 file changed, 6 insertions(+), 5 deletions(-)

Comments

Seth Forshee May 15, 2019, 1:03 p.m. UTC | #1
On Fri, Apr 26, 2019 at 09:31:31PM +0000, Peter Oh wrote:
> From: Peter Oh <peter.oh@bowerswilkins.com>
> 
> Update power limit as documented in:
> http://www.law.go.kr/%ED%96%89%EC%A0%95%EA%B7%9C%EC%B9%99/
> %EC%8B%A0%EA%B3%A0%ED%95%98%EC%A7%80%EC%95%84%EB%8B%88%ED
> %95%98%EA%B3%A0%EA%B0%9C%EC%84%A4%ED%95%A0%EC%88%98%EC%9E
> %88%EB%8A%94%EB%AC%B4%EC%84%A0%EA%B5%AD%EC%9A%A9%EB%AC%B4
> %EC%84%A0%EA%B8%B0%EA%B8%B0/(2018-89,20181227)
> which revised on December 27, 2018.
> 
> Signed-off-by: Peter Oh <peter.oh@bowerswilkins.com>
> ---
>  db.txt | 11 ++++++-----
>  1 file changed, 6 insertions(+), 5 deletions(-)
> 
> diff --git a/db.txt b/db.txt
> index 4fb1948..8d24305 100644
> --- a/db.txt
> +++ b/db.txt
> @@ -695,11 +695,12 @@ country KP: DFS-JP
>  	(5735 - 5815 @ 20), (30)
>  
>  country KR: DFS-JP
> -	(2402 - 2482 @ 40), (13)
> -	(5170 - 5250 @ 80), (20), AUTO-BW
> -	(5250 - 5330 @ 80), (20), DFS, AUTO-BW
> -	(5490 - 5710 @ 160), (30), DFS
> -	(5735 - 5835 @ 80), (30)
> +	# ref: https://www.rra.go.kr
> +	(2402 - 2482 @ 40), (23)
> +	(5170 - 5250 @ 80), (23), AUTO-BW
> +	(5250 - 5330 @ 80), (23), DFS, AUTO-BW
> +	(5490 - 5710 @ 160), (23), DFS
> +	(5735 - 5835 @ 80), (23)

Is there any mention of transmit power control in the document? The fact
that some of the old limits are exactly half of they values you've given
makes me wonder if they weren't set lower for TPC, especially for
5250-5350 MHz where TPC is common.

Since you're changing these rules, I'd also like to see the frequency
ranges changed to match the documented ranges, i.e.:

 2400 - 2483.5
 5150 - 5250
 5250 - 5350
 5470 - 5710
 5735 - 5850

I left the gap in the 5470-5850 MHz range since I can't tell exactly
where the DFS requirement ends. Usually it seems to be 5725 MHz, but
that is not universal. If you can determine where the break is those
ranges could also be expanded.

Thanks,
Seth
Seth Forshee May 15, 2019, 4:21 p.m. UTC | #2
You dropped Peter and the linux-wireless list from your reply, adding
them back.

On Thu, May 16, 2019 at 12:10:16AM +0900, suchan wrote:
> 
> 2019-05-15 10:03PM at Seth Forshee wrote:
> > 
> > Is there any mention of transmit power control in the document? The fact
> > that some of the old limits are exactly half of they values you've given
> > makes me wonder if they weren't set lower for TPC, especially for
> > 5250-5350 MHz where TPC is common.
> > 
> > Since you're changing these rules, I'd also like to see the frequency
> > ranges changed to match the documented ranges, i.e.:
> > 
> >   2400 - 2483.5
> >   5150 - 5250
> >   5250 - 5350
> >   5470 - 5710
> >   5735 - 5850
> > 
> > I left the gap in the 5470-5850 MHz range since I can't tell exactly
> > where the DFS requirement ends. Usually it seems to be 5725 MHz, but
> > that is not universal. If you can determine where the break is those
> > ranges could also be expanded.
> > 
> > Thanks,
> > Seth
> > 
> > _______________________________________________
> > wireless-regdb mailing list
> > wireless-regdb@lists.infradead.org
> > http://lists.infradead.org/mailman/listinfo/wireless-regdb
> 
> from same document, just under the table for wifi range itself 5250∼5350
> MHz and 5470∼5725 MHz need TPC and DFS
> 
> TPC rule is if power exceeds 25mW/MHz (this includes antenna gain), it
> has do be able to reduce it under 12.5mW/Mhz.
> 
> DFS rule itself (DFS-JP) looks right.

Thanks! Based on that I think this is probably what we need:

 (2400 - 2483.5 @ 40), (23)
 (5150 - 5250 @ 80), (23), AUTO-BW
 (5250 - 5350 @ 80), (20), DFS, AUTO-BW
 (5470 - 5725 @ 160), (20), DFS
 (5725 - 5835 @ 80), (23)

Peter, if that looks good to you please send a v3 patch.

Thanks,
Seth
Peter Oh May 15, 2019, 7:08 p.m. UTC | #3
On 05/15/2019 09:21 AM, Seth Forshee wrote:
> You dropped Peter and the linux-wireless list from your reply, adding
> them back.
>
> On Thu, May 16, 2019 at 12:10:16AM +0900, suchan wrote:
>> 2019-05-15 10:03PM at Seth Forshee wrote:
>>> Is there any mention of transmit power control in the document? The fact
>>> that some of the old limits are exactly half of they values you've given
>>> makes me wonder if they weren't set lower for TPC, especially for
>>> 5250-5350 MHz where TPC is common.
>>>
>>> Since you're changing these rules, I'd also like to see the frequency
>>> ranges changed to match the documented ranges, i.e.:
>>>
>>>    2400 - 2483.5
>>>    5150 - 5250
>>>    5250 - 5350
>>>    5470 - 5710
>>>    5735 - 5850
>>>
>>> I left the gap in the 5470-5850 MHz range since I can't tell exactly
>>> where the DFS requirement ends. Usually it seems to be 5725 MHz, but
>>> that is not universal. If you can determine where the break is those
>>> ranges could also be expanded.
>>>
>>> Thanks,
>>> Seth
>>>
>>> _______________________________________________
>>> wireless-regdb mailing list
>>> wireless-regdb@lists.infradead.org
>>> http://lists.infradead.org/mailman/listinfo/wireless-regdb
>> from same document, just under the table for wifi range itself 5250∼5350
>> MHz and 5470∼5725 MHz need TPC and DFS
>>
>> TPC rule is if power exceeds 25mW/MHz (this includes antenna gain), it
>> has do be able to reduce it under 12.5mW/Mhz.
>>
>> DFS rule itself (DFS-JP) looks right.
DFS bandwidth is correct although the rules(radar types and etc.) are 
different from JP, but no plan yet to add KR rules to DFS (requires 
kernel space patches).
> Thanks! Based on that I think this is probably what we need:
>
>   (2400 - 2483.5 @ 40), (23)
>   (5150 - 5250 @ 80), (23), AUTO-BW
>   (5250 - 5350 @ 80), (20), DFS, AUTO-BW
>   (5470 - 5725 @ 160), (20), DFS
>   (5725 - 5835 @ 80), (23)
>
> Peter, if that looks good to you please send a v3 patch.
It looks good to me, too. I'll do v3.

Thanks,
Peter
diff mbox series

Patch

diff --git a/db.txt b/db.txt
index 4fb1948..8d24305 100644
--- a/db.txt
+++ b/db.txt
@@ -695,11 +695,12 @@  country KP: DFS-JP
 	(5735 - 5815 @ 20), (30)
 
 country KR: DFS-JP
-	(2402 - 2482 @ 40), (13)
-	(5170 - 5250 @ 80), (20), AUTO-BW
-	(5250 - 5330 @ 80), (20), DFS, AUTO-BW
-	(5490 - 5710 @ 160), (30), DFS
-	(5735 - 5835 @ 80), (30)
+	# ref: https://www.rra.go.kr
+	(2402 - 2482 @ 40), (23)
+	(5170 - 5250 @ 80), (23), AUTO-BW
+	(5250 - 5330 @ 80), (23), DFS, AUTO-BW
+	(5490 - 5710 @ 160), (23), DFS
+	(5735 - 5835 @ 80), (23)
 	# 60 GHz band channels 1-4,
 	# ref: http://www.law.go.kr/%ED%96%89%EC%A0%95%EA%B7%9C%EC%B9%99/%EB%AC%B4%EC%84%A0%EC%84%A4%EB%B9%84%EA%B7%9C%EC%B9%99
 	(57000 - 66000 @ 2160), (43)