| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
| |
Signed-off-by: Hugo Hromic <hhromic@gmail.com>
|
| |
|
|
|
|
|
|
|
|
|
| |
Currently, we are installing the rpi custom txt and fw files whenever
the meta-raspberrypi layer is included in bblayers.conf. This breaks
other machines that need to use the bcm43430 drivers but with alternate
txt or fw files.
Install these files only when "rpi" is in MACHINEOVERRIDES.
Signed-off-by: Martin Kelly <mkelly@xevo.com>
|
| |
|
|
|
|
|
| |
Use standard /lib variable name and avoid
QA errors when usermerge DISTRO_FEATURE is enabled.
Signed-off-by: Michael Gloff <mgloff@hotmail.com>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The version of this firmware provided by linux-firmware is 7.45.41.26. This
version seems to have connectivity issues when bonding interfaces. Raspbian
included an updated version (7.45.41.46) which tested, proved to fix this
problem (see https://github.com/resin-os/meta-resin/issues/812).
The version Raspbian is providing is not yet in linux-firmware as they have it
directly from Cypress (see https://github.com/RPi-Distro/repo/issues/88).
Besides the issue described above, it fixes various other issues including a
broadpwn fix.
Hopefully this version, or a newer one, will end up in upstream soon. In order
to catch when that happens and stop overwriting this firmware, a check is added
in the racipe based on the md5sum of the current shipped firmware.
In terms of ditribution license, we got an informal one in the github thread
mentioned above.
Signed-off-by: Andrei Gherzan <andrei@gherzan.com>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Currently the firmware is installed but kernel fails to load it
due this .txt file missing in the firmware directory and it ends
up with wifi/bluetooth i/f not being initialized. The error is
also in dmesg
[ 3.120991] usbcore: registered new interface driver brcmfmac
[ 3.148240] brcmfmac mmc1:0001:1: Direct firmware load for brcm/brcmfmac43430-sdio.txt failed with error -2
After applying this patch now ifconfig -a can list wlan0 interface
successfully.
Signed-off-by: Khem Raj <raj.khem@gmail.com>
|
| |
|
|
|
|
|
|
| |
OE-core already bumped the base rev on linux-firmware package
to include the upstreamed version of brcmfmac43430 firmware in
september via OE-Core commit a0bc732976670810505286ba43feee70e2c812ce
Signed-off-by: Khem Raj <raj.khem@gmail.com>
|
| |
|
|
|
|
|
|
|
|
|
| |
The NO_GENERIC_LICENSE map value for Firmware-broadcom_brcm80211 needs
to have the full path to LICENSE.broadcom_brcm80211 from the URL
instead of just the filename.
Fixes the following warning building the linux-firmware recipe:
WARNING: linux-firmware-1_0.0+gitAUTOINC+42ad5367dd-r0 do_populate_lic: linux-firmware: No generic license file exists for: Firmware-broadcom_brcm80211 in any provider
Signed-off-by: Jonathan Liu <net147@gmail.com>
|
| |
|
|
|
|
|
|
|
| |
The license for brcm43430-license should be the license it contains
instead of all the licenses of the linux-firmware packages.
[YOCTO #10251]
Signed-off-by: Jonathan Liu <net147@gmail.com>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
The current version of the recipe produces the following warnings while createing an image:
WARNING: The license listed Firmware-broadcom_brcm80211 was not in the licenses collected for recipe linux-firmwa
re
WARNING: [log_check] td-core-image: found a warning message in the logfile (keyword 'WARNING:'):
[log_check] WARNING: The license listed Firmware-broadcom_brcm80211 was not in the licenses collected for recipe
linux-firmware
This commit contains a rework of the brcm80211 firmware handling and deploys the firmware and the LICENSE files that fixes the warning messages.
Signed-off-by: Tom Doehring <toolmmy@gmail.com>
|
|
|
Signed-off-by: Theodor Gherzan <theodor@resin.io>
|
