[Buildroot] [PATCH] rpi-wifi-firmware: new package

[Peter Korsgaard <peter@korsgaard.com>]

>>>>> "Yann" == Yann E MORIN <yann.morin.1998@free.fr> writes:

 > Peter, All,
 > On 2017-05-05 20:37 +0200, Peter Korsgaard spake thusly:
 >> Add firmware (NVRAM data) for the Raspberry Pi 3 and Zero W wifi module.
 >> 
 >> Notice that linux-firmware provides the main firmware
 >> (brcmfmac43430-sdio.bin), but the module also needs board specific
 >> configuration (NVRAM) data.
 >> 
 >> For the rpi, this data is available in the RPI firmware-nonfree git repo.
 >> As this repo contains a lot of unrelated data (~70MB), simply download the
 >> single NVRAM file instead of cloning the entire repo.
 >> 
 >> A similar approach is used by openwrt and opensuse:
 >> 
 >> https://dev.openwrt.org/browser/trunk/package/firmware/brcmfmac43430-firmware/Makefile?rev=49139
 >> https://build.opensuse.org/package/view_file/hardware/bcm43xx-firmware/bcm43xx-firmware.spec?rev=b1628448b36c85abc9215eab4785ef29
 >> 
 >> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
 > [--SNIP--]
 >> diff --git a/package/rpi-wifi-firmware/Config.in b/package/rpi-wifi-firmware/Config.in
 >> new file mode 100644
 >> index 000000000..2c87c7584
 >> --- /dev/null
 >> +++ b/package/rpi-wifi-firmware/Config.in
 >> @@ -0,0 +1,10 @@
 >> +config BR2_PACKAGE_RPI_WIFI_FIRMWARE
 >> +	bool "rpi-wifi-firmware"
 >> +	depends on BR2_arm || BR2_aarch64

 > I know it read "rpi-wifi-firmware" and thus it is arm or aarch64. But
 > can we expect the same chip to be used on a non-arm board?

Posssibly, yes - But then with different nvram settings. See the
opensuse link above for how they handle rpi + a few sunxi boards.


 > I would just drop the architecture dependency here, because there is
 > nothing specific to the SoC here; the WiFi chip is a secondary chip, so
 > could well be present on other boards that are non-arm.

I disagree. I haven't found any detailed documentation, but my
understanding is that this nvram data is board(-family) specific,
E.G. it differs between the sunxi boards. From what I could find, the
rpi0-w uses the same nvram file as rpi3 though.


 >> +++ b/package/rpi-wifi-firmware/rpi-wifi-firmware.mk
 >> @@ -0,0 +1,22 @@
 >> +################################################################################
 >> +#
 >> +# rpi-wifi-firmware
 >> +#
 >> +################################################################################
 >> +
 >> +RPI_WIFI_FIRMWARE_VERSION = 54bab3d6a6d43239c71d26464e6e10e5067ffea7
 >> +# brcmfmac43430-sdio.bin comes from linux-firmware
 >> +RPI_WIFI_FIRMWARE_SOURCE = brcmfmac43430-sdio.txt
 >> +# git repo contains a lot of unrelated files
 >> +RPI_WIFI_FIRMWARE_SITE =
 >> https://raw.githubusercontent.com/RPi-Distro/firmware-nonfree/$(RPI_WIFI_FIRMWARE_VERSION)/brcm80211/brcm

 > License?

Yeah, that's where things get complicated. There is no explicit license
given. The other brcm*bin files in linux-firmware are covered by
LICENCE.broadcom_bcm43xx, but the question is if this also applies to
this nvram file.

Maybe we should just do:

RPI_WIFI_FIRMWARE_LICENSE = PROPRIETARY

Like we do for the bluetooth part.

-- 
Bye, Peter Korsgaard