[Resending because I sent to the wrong email address for the oe-core mailing list]
NVRAM files for the 43430 modules have been committed into the upstream Linux firmware repo. I'd like to add these files into the linux-firmware recipe. The following files exist upstream on kernel.org: - brcm/brcmfmac43430-sdio.AP6212.txt - brcm/brcmfmac43430-sdio.MUR1DX.txt The AP6212 and MUR1DX are the module types for variants of the 43430 chips. The first patch is a simple update to the latest upstream. I guess someone else will commit a similar change before I get to it, but for now, I need to make the update to test my changes, so I thought I'd send the patch with my RFC series. The second patch adds both NVRAM files into a single new variable. Ideally, the Linux kernel will be extended detect the module type, so having all the NVRAM files in /lib/firmware/brcm seems like a sensible thing to do. But advice here is appreciated. Perhaps I should have a separate variable for each file and allow the machine config to choose which configs to include in the filesystem, similar to how the .bin files are included since Martin Jansa's change? The 3rd patch is trickier, I think. At the moment, the Linux kernel expects there to be only one NVRAM file, named brcmfmac43430-sdio.txt. So to make the system "just work", it seems sensible to provide a way to softlink the module specific NVRAM to the generic filename. I'm trying to avoid each machine type having to define a softlink _append in its own config. Many different machines can use the same module type, for example. I'm just not convinced that the way I've done it is appropriate. eg. I don't like the usage of MACHINEOVERRIDE, or the variable name I've chosen. I'd hoped to do it using a MACHINE_EXTRA_RRECOMMENDS, but I'm not sure if that is possible. Again, advice is appreciated. Ryan Harkin (3): linux-firmware: upgrade to 1d17c18 revision linux-firmware: add BCM43430 nvram files linux-firmware: MACHINEOVERRIDES for BCM43430 NVRAM .../linux-firmware/linux-firmware_git.bb | 23 +++++++++++++++++++--- 1 file changed, 20 insertions(+), 3 deletions(-) -- 2.7.4 -- _______________________________________________ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core