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@xxxxxxxxxxxxxxxxxxx >>> 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
