The "cd ${D}${nonarch_base_libdir}/firmware/brcm/" doesn't seem to be
needed, just include the path in 2nd ln parameter.On Wed, Aug 22, 2018 at 6:30 PM Ryan Harkin <[email protected]> wrote: > 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 <[email protected]> > --- > 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 > >
-- _______________________________________________ Openembedded-core mailing list [email protected] http://lists.openembedded.org/mailman/listinfo/openembedded-core
