summaryrefslogtreecommitdiffstats
path: root/recipes-kernel/linux-firmware
Commit message (Collapse)AuthorAgeFilesLines
* linux-firmware: remove duplicate ${PN}-bcm43455 packageMartin Jansa2018-08-101-1/+8
| | | | Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
* linux-firmware: move ${PN}-cypress-license handling to oe-core recipeMartin Jansa2018-08-101-15/+0
| | | | | | | | | | * this will make this bbappend a bit more version agnostic * depends on oe-core commits from: http://lists.openembedded.org/pipermail/openembedded-core/2018-July/153164.html to prevent including ${PN}-cypress-license package twice in PACKAGES http://lists.openembedded.org/pipermail/openembedded-core/2018-July/153165.html Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
* linux-firmware: update LIC_FILES_CHKSUM for d114732 revision from oe-coreMartin Jansa2018-07-201-1/+1
| | | | | | | | | | | | | | | | | | | | | | * unfortunately the LICENCE.cypress was updated in last upgrade: http://git.openembedded.org/openembedded-core/commit/?id=6be8744d1b8ee35eb47acd517cfa29b2a7f455d5 ba51e86 Update Cypress license termination clause https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/LICENCE.cypress?id=ba51e861f4444f51e7e83f778575a8146dc514d0 * and the same was now backported to sumo branch: http://git.openembedded.org/openembedded-core/commit/?h=sumo&id=087a50f4d8075a91fa6aa373a3dc05017e62f1f9 * it's unfortunate, because now meta-raspberrypi/master is compatible only with oe-core master after 6be8744d1b8ee35eb47acd517cfa29b2a7f455d5 it would be nice to upstream some of these changes to linux-firmware recipes and leave only the rpi specific packaging here * and the same happened with sumo backport, so meta-raspberrypi/sumo will be compatible only with oe-core sumo after 087a50f4d8075a91fa6aa373a3dc05017e62f1f9 Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
* linux-firmware: restore and merge bluez-firmwarePeter A. Bigot2018-05-142-55/+77
| | | | | | | | | | | | The attempt to Raspbian updated firmware blobs in packages separate from linux-firmware introduced unresolvable conflicts with the standard linux-firmware roll-up package. Revert to using an augmented linux-firmware recipe that overrides and adds firmware from two Raspbian repositories that have up-to-date images. Closes #244 Signed-off-by: Peter A. Bigot <pab@pabigot.com>
* Drop unnecessary dependencies and tasksPaul Barker2018-04-231-0/+2
| | | | | | | | | | | | | | We have a few recipes which only deploy files that go into the boot partition and do not create packages to be installed into the rootfs. These recipes don't need to run the usual packaging tasks so we can drop them to speed up the build a little. We also have a bunch of recipes that don't need the usual toolchain as they just copy files or invoke native commands like `mkimage`. So to speed up the build a little more we can set INHIBIT_DEFAULT_DEPS to avoid an unnecessary dependency on the toolchain. Signed-off-by: Paul Barker <pbarker@toganlabs.com>
* linux-firmware: Remove as replaced by linux-firmware-raspbianAndrei Gherzan2018-03-293-85/+0
| | | | Signed-off-by: Andrei Gherzan <andrei@gherzan.com>
* linux-firmware-raspbian: New recipe which uses RPi-Distro repositoryAndrei Gherzan2018-03-291-0/+53
| | | | | | | | This packages only the firmware needed for the RaspberryPi boards. We use the RPi-Distro as it's already maintained by the Raspbian guys and we get better support for the RaspberryPi needed firmwares. Signed-off-by: Andrei Gherzan <andrei@gherzan.com>
* linux-firmware: fix addition of NVRAM file to image (fixes #184)Hugo Hromic2018-02-051-1/+1
| | | | Signed-off-by: Hugo Hromic <hhromic@gmail.com>
* linux-firmware: make rpi fw specific to rpiMartin Kelly2018-01-221-20/+20
| | | | | | | | | | | 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>
* linux-firmware: Replace /lib with ${nonarch_base_libdir}Michael Gloff2017-10-271-4/+4
| | | | | | | Use standard /lib variable name and avoid QA errors when usermerge DISTRO_FEATURE is enabled. Signed-off-by: Michael Gloff <mgloff@hotmail.com>
* linux-firmware: Update brcmfmac43430 to 7.45.41.46Andrei Gherzan2017-09-213-20/+27
| | | | | | | | | | | | | | | | | | | | | 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>
* linux-firmware: Bring up wifi/ble interface on rpi3Khem Raj2017-02-162-0/+78
| | | | | | | | | | | | | | | 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>
* linux-firmware_git.bbappend: DeleteKhem Raj2016-11-084-305/+0
| | | | | | | | 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>
* linux-firmware: Fix "No generic license file exists" warningJonathan Liu2016-10-311-1/+1
| | | | | | | | | | | 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>
* linux-firmware: Correct the LICENSE for brcm43430-licenseJonathan Liu2016-10-311-0/+1
| | | | | | | | | 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>
* linux-firmware: Rework of brcmfmac43430 firmware handlingtoolmmy2016-04-131-8/+12
| | | | | | | | | | | | | | 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>
* linux-firmware: Add brcmfmac43430 firmwareTheodor Gherzan2016-03-104-0/+300
Signed-off-by: Theodor Gherzan <theodor@resin.io>
generated by cgit v1.2.3-54-g00ecf (git 2.39.0) at 2025-07-21 06:08:07 +0000