The linux-raspberrypi 4.1 recipe has been broken for a while, probably since
09b76a43f6. It should now be safe to drop this
version.
Signed-off-by: Paul Barker <paul@paulbarker.me.uk>
DISTRO_TYPE doesn't seem to be set anywhere in OE/poky. This causes
CMDLINE_DEBUG to default to "debug" which is very noisy. This is
especially true when building a systemd based system, as systemd
also looks at the kernel commandline to set the debug level.
Such a system is nearly unuseable from the serial console due
to the amount of data logged by systemd.
Signed-off-by: Frank Meerkoetter <meerkoetter@googlemail.com>
Signed-off-by: Andrei Gherzan <andrei@gherzan.ro>
The rpi-4.8.y branch of git://github.com/raspberrypi/linux.git was rebased,
losing any previous commit hashes. This latest update doesn't include the
raspberry pi patches for 4.8.6, but the upstream patches are included starting
with 4.8.11.
Signed-off-by: Trevor Woerner <twoerner@gmail.com>
Signed-off-by: Andrei Gherzan <andrei@gherzan.ro>
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>
Kernel 4.4.6+ on RaspberryPi support .dtbo files for overlays, instead of .dtb.
Patch the kernel, which has faulty rules to generate .dtbo the way yocto does
Signed-off-by: Herve Jourdain <herve.jourdain@neuf.fr>
Recent versions of the Raspberry Pi firmware can directly handle kernel images
which use device tree. The modifications made by rpi-mkimage are no longer
needed.
Signed-off-by: Paul Barker <paul@paulbarker.me.uk>
Avoids warnings like this with python3:
WARNING: .../meta-raspberrypi/recipes-kernel/linux/linux-raspberrypi_3.18.bb:
<string>:16: ResourceWarning: unclosed file <_io.TextIOWrapper
name='.../meta-raspberrypi/recipes-kernel/linux/linux-raspberrypi/defconfig'
mode='r' encoding='UTF-8'>
Signed-off-by: Jonathan Liu <net147@gmail.com>
Additionally add few few file systems e.g. squashfs, overlayfs
to support booting with initramfs
Drop checking for target triplet to set EABI, rpi probaly should
not have any legacy into OABI world.
Signed-off-by: Khem Raj <raj.khem@gmail.com>
The driver for 8250 defaults to 9600. We setup it on 115200 to be consistent
with getty configuration.
The firmware can do its magic with kgdboc too as it searches and replaces
=serial0 and =serial1. So, use serial0 for kgdboc too.
Signed-off-by: Andrei Gherzan <andrei@gherzan.ro>
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>
Khem Raj
Paul Barker
Andrei Gherzan
Frank Meerkoetter
Trevor Woerner
piotr.lewicki
Jonathan Liu
Andreas Müller
Herve Jourdain
Theodor Gherzan
toolmmy
Alan Stice