unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Brice Waegeneire <brice@waegenei.re>
Cc: me@tobias.gr, 49649@debbugs.gnu.org
Subject: [bug#49649] [PATCH v2 0/4] Load wireless regulatory database in kernel
Date: Fri, 31 Dec 2021 15:29:57 +0100	[thread overview]
Message-ID: <871r1srgnu.fsf@gnu.org> (raw)
In-Reply-To: <20211225184418.9341-1-brice@waegenei.re> (Brice Waegeneire's message of "Sat, 25 Dec 2021 19:44:18 +0100")

Hi Brice,

Brice Waegeneire <brice@waegenei.re> skribis:

> Following Tobias corrections, I've extended the previous patch to correctly
> enable loading of the wireless regulatory database ('regulatory.db') used by
> the kernel subsystem cfg80211, for linux >4.14.  As suggested by Ludo, we now
> build 'regulatory.db' ourselve to make sure it's reproducible and reuse
> upstream signature.  That way the linux kernel correctly load the wireless
> regulatory database at boot which allows us to use a regulatory domain
> different than the "00" default by using a kernel argument such as
> “cfg80211.ieee80211_regdom=FR“.

Does that mean it’s up to users to add such an argument to
‘kernel-arguments’?  If so, we should probably document it (though
that’s not a blocker for this series.)

> This patch doesn't change anything for kernels older than 4.15 for which the
> use of CRDA is needed to load the regulatory database through the
> 'regulatory.bin' file.  IOW the database used by CRDA, is still unsigned and
> CRDA doesn't check signatures for it.

Sounds good.

I haven’t actually tested it but the patch series LGTM!  It’s a much
welcome improvement.

> Fixes <https://issues.guix.gnu.org/49611.

Make sure to add this line in the commit log of patch #2.

Thank you!

Ludo'.




  parent reply	other threads:[~2021-12-31 14:31 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-19 21:15 [bug#49649] [PATCH] gnu: Add regulatory.db in %base-firmware Brice Waegeneire
2021-07-20 13:26 ` Ludovic Courtès
2021-07-20 21:02   ` Brice Waegeneire
2021-07-20 21:56     ` Tobias Geerinckx-Rice via Guix-patches via
2021-07-23  9:11       ` Ludovic Courtès
2021-07-23  9:55         ` Tobias Geerinckx-Rice via Guix-patches via
2021-12-25 18:44 ` [bug#49649] [PATCH v2 0/4] Load wireless regulatory database in kernel Brice Waegeneire
2021-12-28  7:15   ` Leo Famulari
2021-12-31 14:29   ` Ludovic Courtès [this message]
2022-06-01 20:29     ` [bug#49649] [PATCH] gnu: Add regulatory.db in %base-firmware Ludovic Courtès
2021-12-25 18:44 ` [bug#49649] [PATCH v2 1/4] " Brice Waegeneire
2021-12-25 18:44 ` [bug#49649] [PATCH v2 2/4] gnu: wireless-regdb: Reuse 'regulatory.db' signature Brice Waegeneire
2021-12-25 18:44 ` [bug#49649] [PATCH v2 3/4] gnu: wireless-regdb: Update to 2021.08.28 Brice Waegeneire
2021-12-25 18:44 ` [bug#49649] [PATCH v2 4/4] gnu: crda: Describe it as obsolete Brice Waegeneire
2021-12-25 21:13   ` Leo Famulari

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

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=871r1srgnu.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=49649@debbugs.gnu.org \
    --cc=brice@waegenei.re \
    --cc=me@tobias.gr \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).