From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Konstantin Aladyshev <aladyshev22@gmail.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH] configs/pc_x86_64_{bios, efi}_defconfig: add wireless regdb
Date: Wed, 1 May 2024 21:07:28 +0200 [thread overview]
Message-ID: <20240501210728.7fe0ab6a@windsurf> (raw)
In-Reply-To: <20240330212200.794927-1-aladyshev22@gmail.com>
On Sun, 31 Mar 2024 00:22:00 +0300
Konstantin Aladyshev <aladyshev22@gmail.com> wrote:
> Wireless regulatory database lists the allowed radio frequencies for
> each local jurisdiction. Since linux-4.15 the kernel supports loading
> the files regulatory.db/regulatory.db.p7s directly from the
> /lib/firmware directory. Currently this package is not enabled and
> kernel complains with the following message on every boot:
> """
> platform regulatory.0: Direct firmware load for regulatory.db failed
> with error -2
> cfg80211: failed to load regulatory.db
> """
> Add wireless regulatory database package to fix the issue.
>
> Signed-off-by: Konstantin Aladyshev <aladyshev22@gmail.com>
> ---
> configs/pc_x86_64_bios_defconfig | 1 +
> configs/pc_x86_64_efi_defconfig | 1 +
> 2 files changed, 2 insertions(+)
Sorry for the long delay: patch applied. Thanks!
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2024-05-01 19:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-30 21:22 [Buildroot] [PATCH] configs/pc_x86_64_{bios, efi}_defconfig: add wireless regdb Konstantin Aladyshev
2024-05-01 19:07 ` Thomas Petazzoni via buildroot [this message]
2024-05-15 15:28 ` Peter Korsgaard
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=20240501210728.7fe0ab6a@windsurf \
--to=buildroot@buildroot.org \
--cc=aladyshev22@gmail.com \
--cc=thomas.petazzoni@bootlin.com \
/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