public inbox for wireless-regdb@lists.infradead.org
 help / color / mirror / Atom feed
From: Seth Forshee <seth@forshee.me>
To: "Tuck, Lawrence J C (Lawrence)" <ljctuck@avaya.com>
Cc: "wireless-regdb@lists.infradead.org"
	<wireless-regdb@lists.infradead.org>
Subject: Re: [wireless-regdb] wireless-regdb: master-2022-02-18
Date: Wed, 23 Mar 2022 12:29:49 -0500	[thread overview]
Message-ID: <YjtZDaOBpde9uX3v@ubuntu-x1> (raw)
In-Reply-To: <BY5PR15MB4787741965BC6008B3851A35B7189@BY5PR15MB4787.namprd15.prod.outlook.com>

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


  reply	other threads:[~2022-03-23 17:29 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 [this message]
2022-03-23 18:45   ` [wireless-regdb] [External]Re: " Tuck, Lawrence J C (Lawrence)
2022-03-23 19:34     ` Seth Forshee

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=YjtZDaOBpde9uX3v@ubuntu-x1 \
    --to=seth@forshee.me \
    --cc=ljctuck@avaya.com \
    --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