linux/meta-raspberrypi.git/classes, branch dunfell

sdcard_image-rpi.bbclass: Fix when RPI_SDIMG_EXTRA_DEPENDS not defined

2020-08-10T10:10:11+00:00

If the variable is not defined, bitbake will fail: [...] Task 'depends' should be specified in the form 'packagename:task' [...] This is because not expanding the variable leaves an invalid entry. Signed-off-by: Andrei Gherzan

Generalize the naming of the bootfiles deploy directory

2020-08-10T10:10:11+00:00

The raspberry pi 4 variant has a BCM2711 chip, however it still uses the same boot files as the BCM2835 used in previous generations. This change generalizes the naming of the directory generated in the $DEPLOY_DIR to avoid the implication that the files are only meant for the BCM2835. Signed-off-by: Jeff Ithier

sdcard_image-rpi.bbclass: enable extensible inclusion into boot

2020-08-10T10:10:11+00:00

Add DEPLOYPAYLOAD, similar to the existing FATPAYLOAD, to enable adding files to the boot partition from the image deploy directory. Files such as hypervisor binaries may not be present (and in fact unwanted) within the root filesystem, so FATPAYLOAD is not sufficient. DEPLOYPAYLOAD is implemented with support for file renaming from the source file in the image deploy directory to the filename written into the boot image. DEPLOYPAYLOAD is a space-separated list of entries for additions, each of which can optionally be colon-separated: : If the colon separator is omitted, the source deploy directory filename is used as the destination filename. The support for specifying the destination filename is used for including Xen, which produces a machine-specific file in the image deploy directory, and is written to the image partition with its expected filename: xen. Files that are to be included from the image deploy directory will be produced by tasks that the do_image_rpi_sdimg[depends] must list, so enable adding entries to that via a new variable: RPI_SDIMG_EXTRA_DEPENDS. These changes enable retiring a Xen-specific Raspberry Pi SD card bbclass from meta-virtualization and have been tested on the Raspberry Pi 4. Signed-off-by: Christopher Clark

Revert "Generalize the naming of the bootfiles deploy directory"

2020-08-10T10:10:11+00:00

This reverts commit a907c3261ef583f898803706cd596d372c6644cb.

Generalize the naming of the bootfiles deploy directory

2020-07-27T17:02:17+00:00

rpi-u-boot-scr: Set u-boot-default-script as provider

2020-04-08T21:32:06+00:00

Add u-boot-default-script to the PROVIDES variable to make easier to replace boot script in another layer just by changing PREFERRED_PROVIDER_u-boot-default-script variable. Set rpi-u-boot-scr as the default provider for meta-raspberrypi. Signed-off-by: Fabio Berton

sdcard_image-rpi.bbclass: Use IMAGE_NAME_SUFFIX variable in SDIMG

2019-12-05T12:45:02+00:00

Use the IMAGE_NAME_SUFFIX variable to build the SDIMG name. Some layers, notably meta-mender, change the IMAGE_NAME_SUFFIX variable to something other that ".rootfs", causing build failures. Signed-off-by: Francois Retief

sdcard_image-rpi.bbclass: make the dep on rpi-config:do_deploy explicit

2019-10-09T16:14:23+00:00

Signed-off-by: Chris Laplante

sdcard_image-rpi.bbclass: use -v for all mcopy calls and add bbfatal in case mcopy fails

2019-08-06T13:18:54+00:00

* I have this in our layer for some time: RPI_KERNEL_DEVICETREE_OVERLAYS_append = " overlays/vc4-fkms-v3d.dtbo" because we're using vc4graphics also on raspberrypi3 and it was working fine until recently. * now the default rpi-base.inc in warrior and master branch includes the same since: https://github.com/agherzan/meta-raspberrypi/commit/37aa050d5a44eb797540ef50408c2ca8e3da6fa0 and do_image_rpi_sdimg started failing with a bit useless log: ... Partition Table: msdos Disk Flags: Number Start End Size Type File system Flags 1 4194kB 46.1MB 41.9MB primary boot, lba 2 46.1MB 1145MB 1099MB primary mkfs.fat: warning - lowercase labels might not work properly with DOS or Windows mkfs.fat 4.1 (2017-01-24) WARNING: exit code 1 from a shell command. * after adding -v to mcopy calls I got slightly better log: ... Copying w1-gpio-pullup.dtbo Copying w1-gpio.dtbo WARNING: exit code 1 from a shell command. * the issue is that mcopy behavior in non-interactive shell is to fail when the target file already exists (sometimes it seems to cause mcopy to hang forever), but when you execute the run.do_image_rpi_sdimg script manually in interactive shell it will nicely show this prompt on stderr: $ dtb=vc4-fkms-v3d.dtbo recipe-sysroot-native/usr/bin/mcopy -i boot.img -s BUILD/deploy/images/raspberrypi3/$dtb ::overlays/$dtb Long file name "vc4-fkms-v3d.dtbo" already exists. a)utorename A)utorename-all r)ename R)ename-all o)verwrite O)verwrite-all s)kip S)kip-all q)uit (aArRoOsSq): o * with the bbfatal the log is finally a bit more useful: ... Copying w1-gpio-pullup.dtbo Copying w1-gpio.dtbo ERROR: mcopy cannot copy TOPDIR/BUILD/deploy/images/raspberrypi3/vc4-fkms-v3d.dtbo into boot.img WARNING: exit code 1 from a shell command. * the only exception is FATPAYLOAD where it was ignoring mcopy with || true before, I've added bbwarn, because even issues like mentioned there "vfat issues like not supporting .~lock files" are probably worth reporting as warning (why would people add .~lock to FATPAYLOAD if it cannot be copied into boot.img) Signed-off-by: Martin Jansa

sdcard_image-rpi: Check for armstub based on machine feature

2019-07-19T19:05:53+00:00

Signed-off-by: Andrei Gherzan