* Re: [wireless-regdb] wireless-regdb: master-2022-02-18
@ 2022-03-23 14:56 Tuck, Lawrence J C (Lawrence)
2022-03-23 17:29 ` Seth Forshee
0 siblings, 1 reply; 4+ messages in thread
From: Tuck, Lawrence J C (Lawrence) @ 2022-03-23 14:56 UTC (permalink / raw)
To: wireless-regdb@lists.infradead.org
In testing this release, I have encountered an error with the US domain.
Mar 4 03:55:41 kernel: [ 1269.508101] cfg80211: Invalid regulatory domain detected:
Mar 4 03:55:41 kernel: [ 1269.508161] cfg80211: Regulatory domain: US
Mar 4 03:55:41 kernel: [ 1269.508185] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time)
Mar 4 03:55:41 kernel: [ 1269.508218] cfg80211: (902000 KHz - 2000 KHz @ 0 KHz), (N/A, 0 mBm), (N/A)
Mar 4 03:55:41 kernel: [ 1269.508510] cfg80211: (904000 KHz - 16000 KHz @ 0 KHz), (N/A, 0 mBm), (N/A)
Mar 4 03:55:41 kernel: [ 1269.508563] cfg80211: (920000 KHz - 8000 KHz @ 0 KHz), (N/A, 0 mBm), (N/A)
Mar 4 03:55:41 kernel: [ 1269.508592] cfg80211: (2400000 KHz - 2472000 KHz @ 40000 KHz), (N/A, 3000 mBm), (N/A)
It looks like the parsing of the S1G frequencies failed. Looking at db.txt there are no spaces around the '-' in the S1G channels. Has anyone else encountered this issue?
Lawrence
-----Original Message-----
From: wireless-regdb <wireless-regdb-bounces@lists.infradead.org> On Behalf Of Seth Forshee
Sent: Friday, February 18, 2022 8:05 PM
To: wireless-regdb@lists.infradead.org
Cc: linux-wireless@vger.kernel.org
Subject: [External][wireless-regdb] [ANN] wireless-regdb: master-2022-02-18
[External Sender]
A new release of wireless-regdb (master-2022-02-18) is available at:
https://urldefense.com/v3/__https://www.kernel.org/pub/software/network/wireless-regdb/wireless-regdb-2022.02.18.tar.xz__;!!AlswS5g!weTIoMMWD2O_5SH5Hdv8O5itCnmv238R8WvBqAEGn6E0B8-VTkDb7ZGzoucXyTk$
The short log of changes since the master-2021-08-28 release is below.
Thanks,
Seth
---
Jiaxun Yang (1):
wireless-regdb: Update regulatory rules for China (CN)
Robert Marko (1):
wireless-regdb: Update regulatory rules for Croatia (HR) on 6GHz
Romain Izard (1):
wireless-regdb: Update regulatory rules for France (FR) on 6 and 60 GHz
Seth Forshee (2):
Revert "wireless-regdb: Update regulatory rules for South Korea (KR)"
wireless-regdb: update regulatory database based on preceding changes
Sultan Alsawaf (1):
wireless-regdb: Raise DFS TX power limit to 250 mW (24 dBm) for the US
Sungbo Eo (2):
wireless-regdb: Update regulatory rules for South Korea (KR)
wireless-regdb: Update regulatory rules for South Korea (KR)
Thomas Pedersen (2):
wireless-regdb: add support for US S1G channels
wireless-regdb: add 802.11ah bands to world regulatory domain
Wilco Baan Hofman (1):
wireless-regdb: Update regulatory rules for the Netherlands (NL) on 6GHz
Xose Vazquez Perez (1):
wireless-regdb: Update regulatory rules for Spain (ES) on 6GHz
_______________________________________________
wireless-regdb mailing list
wireless-regdb@lists.infradead.org
https://urldefense.com/v3/__http://lists.infradead.org/mailman/listinfo/wireless-regdb__;!!AlswS5g!weTIoMMWD2O_5SH5Hdv8O5itCnmv238R8WvBqAEGn6E0B8-VTkDb7ZGzzZBpJ1w$
_______________________________________________
wireless-regdb mailing list
wireless-regdb@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/wireless-regdb
^ permalink raw reply [flat|nested] 4+ messages in thread* Re: [wireless-regdb] wireless-regdb: master-2022-02-18
2022-03-23 14:56 [wireless-regdb] wireless-regdb: master-2022-02-18 Tuck, Lawrence J C (Lawrence)
@ 2022-03-23 17:29 ` Seth Forshee
2022-03-23 18:45 ` [wireless-regdb] [External]Re: " Tuck, Lawrence J C (Lawrence)
0 siblings, 1 reply; 4+ messages in thread
From: Seth Forshee @ 2022-03-23 17:29 UTC (permalink / raw)
To: Tuck, Lawrence J C (Lawrence); +Cc: wireless-regdb@lists.infradead.org
On Wed, Mar 23, 2022 at 02:56:41PM +0000, Tuck, Lawrence J C (Lawrence) wrote:
> In testing this release, I have encountered an error with the US domain.
>
> Mar 4 03:55:41 kernel: [ 1269.508101] cfg80211: Invalid regulatory domain detected:
> Mar 4 03:55:41 kernel: [ 1269.508161] cfg80211: Regulatory domain: US
> Mar 4 03:55:41 kernel: [ 1269.508185] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time)
> Mar 4 03:55:41 kernel: [ 1269.508218] cfg80211: (902000 KHz - 2000 KHz @ 0 KHz), (N/A, 0 mBm), (N/A)
> Mar 4 03:55:41 kernel: [ 1269.508510] cfg80211: (904000 KHz - 16000 KHz @ 0 KHz), (N/A, 0 mBm), (N/A)
> Mar 4 03:55:41 kernel: [ 1269.508563] cfg80211: (920000 KHz - 8000 KHz @ 0 KHz), (N/A, 0 mBm), (N/A)
> Mar 4 03:55:41 kernel: [ 1269.508592] cfg80211: (2400000 KHz - 2472000 KHz @ 40000 KHz), (N/A, 3000 mBm), (N/A)
>
> It looks like the parsing of the S1G frequencies failed. Looking at db.txt there are no spaces around the '-' in the S1G channels. Has anyone else encountered this issue?
I didn't see this in my testing against multiple kernel versions. What
version are you using?
Are you using regulatory.db or regulatory.bin? I only tested
regulatory.bin with regdbdump and not by loading it into a kernel, so
there could be a problem there that I didn't catch.
Thanks,
Seth
_______________________________________________
wireless-regdb mailing list
wireless-regdb@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/wireless-regdb
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [wireless-regdb] [External]Re: wireless-regdb: master-2022-02-18
2022-03-23 17:29 ` Seth Forshee
@ 2022-03-23 18:45 ` Tuck, Lawrence J C (Lawrence)
2022-03-23 19:34 ` Seth Forshee
0 siblings, 1 reply; 4+ messages in thread
From: Tuck, Lawrence J C (Lawrence) @ 2022-03-23 18:45 UTC (permalink / raw)
To: Seth Forshee; +Cc: wireless-regdb@lists.infradead.org
I build it into my custom 4.4.11 kernel with Yocto (Morty release). The regdb.c that was generated with the awk script was incorrect (it matched the output below where the end frequency was replaced by the bandwidth and the bandwidth was 0). I suspect that the awk script used to process db.txt in the linux build processes it differently than the python scripts.
Lawrence
-----Original Message-----
From: Seth Forshee <seth@forshee.me>
Sent: Wednesday, March 23, 2022 1:30 PM
To: Tuck, Lawrence J C (Lawrence) <ljctuck@avaya.com>
Cc: wireless-regdb@lists.infradead.org
Subject: [External]Re: [wireless-regdb] wireless-regdb: master-2022-02-18
[External Sender]
On Wed, Mar 23, 2022 at 02:56:41PM +0000, Tuck, Lawrence J C (Lawrence) wrote:
> In testing this release, I have encountered an error with the US domain.
>
> Mar 4 03:55:41 kernel: [ 1269.508101] cfg80211: Invalid regulatory domain detected:
> Mar 4 03:55:41 kernel: [ 1269.508161] cfg80211: Regulatory domain: US
> Mar 4 03:55:41 kernel: [ 1269.508185] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time)
> Mar 4 03:55:41 kernel: [ 1269.508218] cfg80211: (902000 KHz - 2000 KHz @ 0 KHz), (N/A, 0 mBm), (N/A)
> Mar 4 03:55:41 kernel: [ 1269.508510] cfg80211: (904000 KHz - 16000 KHz @ 0 KHz), (N/A, 0 mBm), (N/A)
> Mar 4 03:55:41 kernel: [ 1269.508563] cfg80211: (920000 KHz - 8000 KHz @ 0 KHz), (N/A, 0 mBm), (N/A)
> Mar 4 03:55:41 kernel: [ 1269.508592] cfg80211: (2400000 KHz - 2472000 KHz @ 40000 KHz), (N/A, 3000 mBm), (N/A)
>
> It looks like the parsing of the S1G frequencies failed. Looking at db.txt there are no spaces around the '-' in the S1G channels. Has anyone else encountered this issue?
I didn't see this in my testing against multiple kernel versions. What version are you using?
Are you using regulatory.db or regulatory.bin? I only tested regulatory.bin with regdbdump and not by loading it into a kernel, so there could be a problem there that I didn't catch.
Thanks,
Seth
_______________________________________________
wireless-regdb mailing list
wireless-regdb@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/wireless-regdb
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [wireless-regdb] [External]Re: wireless-regdb: master-2022-02-18
2022-03-23 18:45 ` [wireless-regdb] [External]Re: " Tuck, Lawrence J C (Lawrence)
@ 2022-03-23 19:34 ` Seth Forshee
0 siblings, 0 replies; 4+ messages in thread
From: Seth Forshee @ 2022-03-23 19:34 UTC (permalink / raw)
To: Tuck, Lawrence J C (Lawrence); +Cc: wireless-regdb@lists.infradead.org
On Wed, Mar 23, 2022 at 06:45:16PM +0000, Tuck, Lawrence J C (Lawrence) wrote:
> I build it into my custom 4.4.11 kernel with Yocto (Morty release). The regdb.c that was generated with the awk script was incorrect (it matched the output below where the end frequency was replaced by the bandwidth and the bandwidth was 0). I suspect that the awk script used to process db.txt in the linux build processes it differently than the python scripts.
Ah, that makes sense. I'll add spaces and get a new regdb released soon.
Thanks,
Seth
>
> Lawrence
>
> -----Original Message-----
> From: Seth Forshee <seth@forshee.me>
> Sent: Wednesday, March 23, 2022 1:30 PM
> To: Tuck, Lawrence J C (Lawrence) <ljctuck@avaya.com>
> Cc: wireless-regdb@lists.infradead.org
> Subject: [External]Re: [wireless-regdb] wireless-regdb: master-2022-02-18
>
> [External Sender]
>
> On Wed, Mar 23, 2022 at 02:56:41PM +0000, Tuck, Lawrence J C (Lawrence) wrote:
> > In testing this release, I have encountered an error with the US domain.
> >
> > Mar 4 03:55:41 kernel: [ 1269.508101] cfg80211: Invalid regulatory domain detected:
> > Mar 4 03:55:41 kernel: [ 1269.508161] cfg80211: Regulatory domain: US
> > Mar 4 03:55:41 kernel: [ 1269.508185] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time)
> > Mar 4 03:55:41 kernel: [ 1269.508218] cfg80211: (902000 KHz - 2000 KHz @ 0 KHz), (N/A, 0 mBm), (N/A)
> > Mar 4 03:55:41 kernel: [ 1269.508510] cfg80211: (904000 KHz - 16000 KHz @ 0 KHz), (N/A, 0 mBm), (N/A)
> > Mar 4 03:55:41 kernel: [ 1269.508563] cfg80211: (920000 KHz - 8000 KHz @ 0 KHz), (N/A, 0 mBm), (N/A)
> > Mar 4 03:55:41 kernel: [ 1269.508592] cfg80211: (2400000 KHz - 2472000 KHz @ 40000 KHz), (N/A, 3000 mBm), (N/A)
> >
> > It looks like the parsing of the S1G frequencies failed. Looking at db.txt there are no spaces around the '-' in the S1G channels. Has anyone else encountered this issue?
>
> I didn't see this in my testing against multiple kernel versions. What version are you using?
>
> Are you using regulatory.db or regulatory.bin? I only tested regulatory.bin with regdbdump and not by loading it into a kernel, so there could be a problem there that I didn't catch.
>
> Thanks,
> Seth
_______________________________________________
wireless-regdb mailing list
wireless-regdb@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/wireless-regdb
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2022-03-23 19:34 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2022-03-23 14:56 [wireless-regdb] wireless-regdb: master-2022-02-18 Tuck, Lawrence J C (Lawrence)
2022-03-23 17:29 ` Seth Forshee
2022-03-23 18:45 ` [wireless-regdb] [External]Re: " Tuck, Lawrence J C (Lawrence)
2022-03-23 19:34 ` Seth Forshee
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox