public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Adolf Belka <adolf.belka@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH v3 8/8] wlanap.cgi: Access db.txt in place of using regdbdump on regulatory.bin
Date: Thu, 05 Aug 2021 12:55:12 +0200	[thread overview]
Message-ID: <cfb085e1-d670-ae30-e2f7-96b67041eeb5@ipfire.org> (raw)
In-Reply-To: <882d3501-5e22-4977-96e0-896dfe6b27b8@ipfire.org>

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

Hi Bernhard,

On 05/08/2021 12:40, Bernhard Bitsch wrote:
> Reviewed-by: Bernhard Bitsch <bbitsch(a)ipfire.org>
> Tested-by: Bernhard Bitsch <bbitsch(a)ipfire.org>
> 
> Am 05.08.2021 um 12:21 schrieb Adolf Belka:
>> - wlanap.cgi was using regdbdump from crda to create a text based list of the
>>     wireless settings by country database.
>> - With the removal of crda as part of the removal of python2 this option could not be
>>     used.
>> - wireless-regdb also has a text based database list in the source tarball and this
>>     patch makes wlanap.cgi read this list into the @countrylist_cmd variable
>> - This needs to be tested by someone that has an IPFire system with wifi that can access
>>     and evaluate wlanap.cgi to confirm that this change functions as expected.
>> - This version changes the name of the stored text file from db.txt to regulatorydb.txt
>> - The command to read the data from regulatorydb.txt into @countrylist_cmd has been
>>     corrected
>>
>> Signed-off-by: Adolf Belka <adolf.belka(a)ipfire.org>
>> ---
>>   html/cgi-bin/wlanap.cgi | 5 ++++-
>>   1 file changed, 4 insertions(+), 1 deletion(-)
>>
>> diff --git a/html/cgi-bin/wlanap.cgi b/html/cgi-bin/wlanap.cgi
>> index eba5fe774..3024257db 100644
>> --- a/html/cgi-bin/wlanap.cgi
>> +++ b/html/cgi-bin/wlanap.cgi
>> @@ -312,8 +312,11 @@ if ( $channel =~ /\d+/ ){push(@temp,$channel + 0);}
>>   push(@channellist, @temp);
>>   }
>> -my @countrylist_cmd = `regdbdump /usr/lib/crda/regulatory.bin 2>/dev/null`;
>>   # get available country codes
>> +open(FILE, “</lib/firmware/firmwaredb.txt”);
> Should read:
> +open(FILE, “</lib/firmware/regulatorydb.txt”);
Thanks so much for spotting this. The power of the review process. I will re-issue the patches.

Regards,
Adolf.
> 
>  > +my @countrylist_cmd = <FILE>;
>> +close(FILE);
>> +
>>   my @temp = "00";
>>   foreach (@countrylist_cmd){
>>

  reply	other threads:[~2021-08-05 10:55 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-05 10:21 [PATCH v3 1/8] make.sh: Remove crda and remaining python2 modules Adolf Belka
2021-08-05 10:21 ` [PATCH v3 2/8] crda: removal from kernel 4.15 and onwards Adolf Belka
2021-08-05 10:21 ` [PATCH v3 3/8] python-m2crypto: removal of python2 module Adolf Belka
2021-08-05 10:21 ` [PATCH v3 4/8] python-typing: Removal of this " Adolf Belka
2021-08-05 10:21 ` [PATCH v3 5/8] python-setuptools: " Adolf Belka
2021-08-05 10:21 ` [PATCH v3 6/8] ipaddr: " Adolf Belka
2021-08-05 10:21 ` [PATCH v3 7/8] wireless-regdb: Use db.txt file for wlanap.cgi Adolf Belka
2021-08-05 10:33   ` Bernhard Bitsch
2021-08-05 10:21 ` [PATCH v3 8/8] wlanap.cgi: Access db.txt in place of using regdbdump on regulatory.bin Adolf Belka
2021-08-05 10:40   ` Bernhard Bitsch
2021-08-05 10:55     ` Adolf Belka [this message]
2021-08-05 20:31       ` Michael Tremer

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=cfb085e1-d670-ae30-e2f7-96b67041eeb5@ipfire.org \
    --to=adolf.belka@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