On 5 March 2014 12:05, Ronald Wahl <ronald.wahl at raritan.com> wrote: > On 05.03.2014 11:32, Janusz Dziedzic wrote: >> >> On 3 March 2014 12:01, Ronald Wahl <ronald.wahl at raritan.com> wrote: >>> >>> This is a port of what Johannes Berg sent to the Linux kernel >>> in May 2013 for the static world regulatory domain. >>> >>> Signed-off-by: Ronald Wahl <ronald.wahl at raritan.com> >>> --- >>> db.txt | 5 ++++- >>> 1 file changed, 4 insertions(+), 1 deletion(-) >>> >>> diff --git a/db.txt b/db.txt >>> index fcab208..9391ff6 100644 >>> --- a/db.txt >>> +++ b/db.txt >>> @@ -7,7 +7,10 @@ country 00: >>> (2474 - 2494 @ 20), (20), NO-IR >>> # Channel 36 - 48 >>> (5170 - 5250 @ 80), (20), NO-IR >> >> @ 160 >>> >>> - # NB: 5260 MHz - 5700 MHz requies DFS >>> + # Channel 52 - 64 >>> + (5250 - 5330 @ 80), (20), NO-IR, DFS >> >> @160 >>> >>> + # Channel 100 - 144 >>> + (5490 - 5730 @ 80), (20), NO-IR, DFS >> >> @160? >>> >>> # Channel 149 - 165 >>> (5735 - 5835 @ 80), (20), NO-IR >>> # IEEE 802.11ad (60GHz), channels 1..3 >>> -- >>> 1.8.5.3 > > > At the moment there are no @ 160 entries at all in the db.txt so I hesitated > to add it for the world regdom. Maybe we should add the @ 160 in a separate > patch for the regdoms where this is appropriate. What do you think? > I think we should set 160 for world regdom - same as kernel do. World regdom freq_diff is not verified for rules, when REQUEST by CORE - workaround? - and such config will be allowed. @Luis ? For the other countries we could not set 160 while freq_diff < 160 for most of the rules and there will be verification in kernel space for that. In such case AUTO-BW flag could be used in the future. That allow auto calculation of max bandwidth base on contiguous freq rules. BR Janusz
