From: Ryan Harkin <ryan.harkin@linaro.org>
To: openembedded-core@lists.openembedded.org
Cc: daiane.angolini@nxp.com, patches@linaro.org
Subject: [RFC 3/3] linux-firmware: MACHINEOVERRIDES for BCM43430 NVRAM
Date: Wed, 22 Aug 2018 17:30:36 +0100 [thread overview]
Message-ID: <1534955436-729-4-git-send-email-ryan.harkin@linaro.org> (raw)
In-Reply-To: <1534955436-729-1-git-send-email-ryan.harkin@linaro.org>
The Linux kernel currently expects a single NVRAM file for BCM43430
named brcmfmac43430-sdio.txt.
Allow the machine to specify an override to link its module specific
NVRAM to the filename expected by the kernel.
Signed-off-by: Ryan Harkin <ryan.harkin@linaro.org>
---
meta/recipes-kernel/linux-firmware/linux-firmware_git.bb | 12 ++++++++++++
1 file changed, 12 insertions(+)
diff --git a/meta/recipes-kernel/linux-firmware/linux-firmware_git.bb b/meta/recipes-kernel/linux-firmware/linux-firmware_git.bb
index 8c54f28..b647abc 100644
--- a/meta/recipes-kernel/linux-firmware/linux-firmware_git.bb
+++ b/meta/recipes-kernel/linux-firmware/linux-firmware_git.bb
@@ -226,6 +226,18 @@ do_install() {
( cd ${D}${nonarch_base_libdir}/firmware ; ln -sf ti-connectivity/* . )
}
+# Adding bcm43430-nvram-{module type} to MACHINEOVERRIDES will create a
+# softlink for the module specific NVRAM file to the filename expected
+# by the Linux kernel
+FILES_${PN}-bcm43430-nvram_append_bcm43430-nvram-mur1dx = " ${nonarch_base_libdir}/firmware/brcm/brcmfmac43430-sdio.txt"
+do_install_append_bcm43430-nvram-mur1dx() {
+ ( cd ${D}${nonarch_base_libdir}/firmware/brcm/ ; ln -sf brcmfmac43430-sdio.MUR1DX.txt brcmfmac43430-sdio.txt)
+}
+FILES_${PN}-bcm43430-nvram_append_bcm43430-nvram-ap6212 = "${nonarch_base_libdir}/firmware/brcm/brcmfmac43430-sdio.txt"
+do_install_append_bcm43430-nvram-ap6212() {
+ ( cd ${D}${nonarch_base_libdir}/firmware/brcm/ ; ln -sf brcmfmac43430-sdio.AP6212.txt brcmfmac43430-sdio.txt)
+}
+
PACKAGES =+ "${PN}-ralink-license ${PN}-ralink \
${PN}-mt7601u-license ${PN}-mt7601u \
--
2.7.4
next prev parent reply other threads:[~2018-08-22 16:30 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-22 16:30 [RFC 0/3] Adding BCM43430 NVRAM files Ryan Harkin
2018-08-22 16:30 ` [RFC 1/3] linux-firmware: upgrade to 1d17c18 revision Ryan Harkin
2018-08-22 16:30 ` [RFC 2/3] linux-firmware: add BCM43430 nvram files Ryan Harkin
2018-08-22 16:30 ` Ryan Harkin [this message]
2018-08-22 16:41 ` [RFC 3/3] linux-firmware: MACHINEOVERRIDES for BCM43430 NVRAM Martin Jansa
2018-08-22 16:47 ` Ryan Harkin
2018-08-22 16:56 ` Martin Jansa
2018-08-22 17:11 ` Ryan Harkin
2018-08-22 19:02 ` Martin Jansa
2018-08-22 20:10 ` Ryan Harkin
2018-08-22 20:36 ` Khem Raj
2018-08-22 21:52 ` Ryan Harkin
2018-08-22 20:42 ` Andre McCurdy
2018-08-22 21:56 ` Ryan Harkin
2018-08-22 22:55 ` Andre McCurdy
2018-08-23 6:12 ` Ryan Harkin
2018-08-23 6:39 ` Martin Hundebøll
2018-08-23 7:08 ` Ryan Harkin
2018-08-23 7:19 ` Andre McCurdy
2018-08-23 15:58 ` Khem Raj
2018-08-23 7:06 ` Andre McCurdy
2018-08-23 7:17 ` Ryan Harkin
2018-08-23 7:34 ` Andre McCurdy
2018-08-23 7:36 ` Ryan Harkin
2018-08-23 8:15 ` Ryan Harkin
2018-08-24 2:53 ` Andre McCurdy
2018-08-24 9:04 ` Martin Jansa
2018-08-24 10:43 ` Mike Looijmans
2018-08-28 10:54 ` Ryan Harkin
2018-08-24 10:50 ` Ryan Harkin
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=1534955436-729-4-git-send-email-ryan.harkin@linaro.org \
--to=ryan.harkin@linaro.org \
--cc=daiane.angolini@nxp.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=patches@linaro.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