Note that I've found dozens of posts on the web that describe the same symptom, and a subset of those arrive at the same conclusion of this bug. I do agree that the license that the github repo holds indicates that the files are made available for personal use, but perhaps we can address that.
For my information, what licenses cover the firmware files we are shipping today in the brcm/ subdirectory that linux-firmware currently installs? Namely:
Note that I've found dozens of posts on the web that describe the same symptom, and a subset of those arrive at the same conclusion of this bug. I do agree that the license that the github repo holds indicates that the files are made available for personal use, but perhaps we can address that.
For my information, what licenses cover the firmware files we are shipping today in the brcm/ subdirectory that linux-firmware currently installs? Namely:
bcm4329- fullmac- 4.bin sdio.bin -sdio.bin -sdio.bin -sdio.bin sdio.bin sdio.bin sdio.bin sdio.bin sdio.bin sdio.bin sdio.bin -sdio.bin sdio.bin sdio.bin pcie.bin pcie.bin sdio.bin pcie.bin sdio.bin pcie.bin pcie.bin pcie.ap. bin pcie.bin pcie.bin pcie.bin pcie.bin sdio.bin
bcm43xx-0.fw
bcm43xx_hdr-0.fw
brcmfmac43143.bin
brcmfmac43143-
brcmfmac43236b.bin
brcmfmac43241b0
brcmfmac43241b4
brcmfmac43241b5
brcmfmac43242a.bin
brcmfmac4329-
brcmfmac4330-
brcmfmac43340-
brcmfmac4334-
brcmfmac4335-
brcmfmac43362-
brcmfmac4339-
brcmfmac43430a0
brcmfmac43430-
brcmfmac43455-
brcmfmac4350c2-
brcmfmac4350-
brcmfmac4354-
brcmfmac43569.bin
brcmfmac4356-
brcmfmac4356-
brcmfmac43570-
brcmfmac4358-
brcmfmac43602-
brcmfmac43602-
brcmfmac4366b-
brcmfmac4366c-
brcmfmac4371-
brcmfmac4373.bin
brcmfmac4373-