From: Christoph Engelbert <me@noctarius.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] <wireless-regdb>: Adds the option to copy "regulatory.db[.p7s]" to /lib/firmware
Date: Fri, 13 Jul 2018 12:32:54 +0300 [thread overview]
Message-ID: <20180713093254.7994-1-me@noctarius.com> (raw)
Certain wireless drivers (like the Broadcom FullMac drivers" expect the regulatory.db and
regulatory.db.p7s files to be available to be loadable from /lib/firmware. If not available
the driver still loads but runs on a minimal subset of channels.
This newly added option gives possibility to have those files copied to the necessary directory.
Signed-off-by: Christoph Engelbert <me@noctarius.com>
---
package/wireless-regdb/wireless-regdb.mk | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/package/wireless-regdb/wireless-regdb.mk b/package/wireless-regdb/wireless-regdb.mk
index e9283a00e2..829374edcf 100644
--- a/package/wireless-regdb/wireless-regdb.mk
+++ b/package/wireless-regdb/wireless-regdb.mk
@@ -15,6 +15,10 @@ define WIRELESS_REGDB_INSTALL_TARGET_CMDS
$(TARGET_DIR)/usr/lib/crda/regulatory.bin
$(INSTALL) -m 644 -D -T $(@D)/sforshee.key.pub.pem \
$(TARGET_DIR)/etc/wireless-regdb/pubkeys/sforshee.key.pub.pem
+ $(INSTALL) -m 644 -D -T $(@D)/regulatory.db \
+ $(TARGET_DIR)/lib/firmware/regulatory.db
+ $(INSTALL) -m 644 -D -T $(@D)/regulatory.db.p7s \
+ $(TARGET_DIR)/lib/firmware/regulatory.db.p7s
endef
$(eval $(generic-package))
--
2.17.1
next reply other threads:[~2018-07-13 9:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-13 9:32 Christoph Engelbert [this message]
2018-07-14 12:38 ` [Buildroot] [PATCH 1/1] <wireless-regdb>: Adds the option to copy "regulatory.db[.p7s]" to /lib/firmware Martin Bark
2018-07-15 8:13 ` Christoph Engelbert
2018-07-15 18:41 ` Martin Bark
2018-07-16 15:15 ` Christoph Engelbert
-- strict thread matches above, loose matches on Subject: below --
2018-07-13 9:30 noctarius
2018-07-12 20:09 noctarius
2018-07-13 8:37 ` Arnout Vandecappelle
2018-07-13 9:22 ` Christoph Engelbert
2018-07-13 9:34 ` Christoph Engelbert
2018-07-12 20:01 noctarius
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=20180713093254.7994-1-me@noctarius.com \
--to=me@noctarius.com \
--cc=buildroot@busybox.net \
/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