public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH v2 7/8] wireless-regdb: Use db.txt file for wlanap.cgi
Date: Wed, 04 Aug 2021 16:34:19 +0200	[thread overview]
Message-ID: <D8534138-73A9-4535-B11B-0DB64652E0AD@ipfire.org> (raw)
In-Reply-To: <20210728172932.2737967-7-adolf.belka@ipfire.org>

[-- Attachment #1: Type: text/plain, Size: 1608 bytes --]

Hello,

This whole patch set looks very good.

I am just wondering if “db.txt” isn’t a bit generic for the file?

Should we not call it /lib/firmware/regulatory.txt?

-Michael

> On 28 Jul 2021, at 19:29, Adolf Belka <adolf.belka(a)ipfire.org> wrote:
> 
> - db.txt is the text file version of the wireless settings by country database
> - Using db.txt means that regdbdump from crda is not required by wlanap.cgi
> - This patch copies the db.txt file from the source tarball to /lib/firmware/ where
>   it can be read by wlanap.cgi
> - Updated rootfile to include db.txt
> 
> Signed-off-by: Adolf Belka <adolf.belka(a)ipfire.org>
> ---
> config/rootfiles/common/wireless-regdb | 1 +
> lfs/wireless-regdb                     | 1 +
> 2 files changed, 2 insertions(+)
> 
> diff --git a/config/rootfiles/common/wireless-regdb b/config/rootfiles/common/wireless-regdb
> index 7e830ae1f..2ebbfc169 100644
> --- a/config/rootfiles/common/wireless-regdb
> +++ b/config/rootfiles/common/wireless-regdb
> @@ -1,3 +1,4 @@
> +lib/firmware/db.txt
> lib/firmware/regulatory.db
> lib/firmware/regulatory.db.p7s
> #usr/lib/crda
> diff --git a/lfs/wireless-regdb b/lfs/wireless-regdb
> index 6cffd34ba..1ef7da231 100644
> --- a/lfs/wireless-regdb
> +++ b/lfs/wireless-regdb
> @@ -72,5 +72,6 @@ $(TARGET) : $(patsubst %,$(DIR_DL)/%,$(objects))
> 	@$(PREBUILD)
> 	@rm -rf $(DIR_APP) && cd $(DIR_SRC) && tar axf $(DIR_DL)/$(DL_FILE)
> 	cd $(DIR_APP) && make install
> +	cp -vf $(DIR_APP)/db.txt /lib/firmware/db.txt
> 	@rm -rf $(DIR_APP)
> 	@$(POSTBUILD)
> -- 
> 2.32.0
> 


  reply	other threads:[~2021-08-04 14:34 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-28 17:29 [PATCH v2 1/8] make.sh: Remove crda and remaining python2 modules Adolf Belka
2021-07-28 17:29 ` [PATCH v2 2/8] crda: removal from kernel 4.15 and onwards Adolf Belka
2021-07-28 17:29 ` [PATCH v2 3/8] python-m2crypto: removal of python2 module Adolf Belka
2021-07-28 17:29 ` [PATCH v2 4/8] python-typing: Removal of this " Adolf Belka
2021-07-28 17:29 ` [PATCH v2 5/8] python-setuptools: " Adolf Belka
2021-07-28 17:29 ` [PATCH v2 6/8] ipaddr: " Adolf Belka
2021-07-28 17:29 ` [PATCH v2 7/8] wireless-regdb: Use db.txt file for wlanap.cgi Adolf Belka
2021-08-04 14:34   ` Michael Tremer [this message]
2021-07-28 17:29 ` [PATCH v2 8/8] wlanap.cgi: Access db.txt in place of using regdbdump on regulatory.bin Adolf Belka
2021-08-04 14:32   ` Michael Tremer
2021-08-04 17:04     ` Adolf Belka

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=D8534138-73A9-4535-B11B-0DB64652E0AD@ipfire.org \
    --to=michael.tremer@ipfire.org \
    --cc=development@lists.ipfire.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