From: "Ludovic Courtès" <ludo@gnu.org>
To: Tobias Geerinckx-Rice <me@tobias.gr>
Cc: 49649@debbugs.gnu.org, Brice Waegeneire <brice@waegenei.re>
Subject: [bug#49649] [PATCH] gnu: Add regulatory.db in %base-firmware.
Date: Fri, 23 Jul 2021 11:11:29 +0200 [thread overview]
Message-ID: <87y29xbdj2.fsf@gnu.org> (raw)
In-Reply-To: <bc6967e5952ce53555817dc17c7f64f8@tobias.gr> (Tobias Geerinckx-Rice's message of "Tue, 20 Jul 2021 23:56:40 +0200")
Hi!
Tobias Geerinckx-Rice <me@tobias.gr> skribis:
>> If we want to be sure such spourious emssions can't
>> happen we need to fix the loading of 'regulatory.db' by the kernel
>
> That's not true. The whole point of the world regulatory domain is to
> be the subset of all other regdb entries.
In that case we have a practical interest in making db loading work, as
this would allow (some) users to use a wider part of the frequency
spectrum.
Thanks for looking into this, comrades!
Ludo’.
next prev parent reply other threads:[~2021-07-23 9:12 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 [this message]
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
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 3/4] gnu: wireless-regdb: Update to 2021.08.28 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 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87y29xbdj2.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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.