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

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

2019-08-14T11:56:20+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-20T20:56:21+00:00

Signed-off-by: Andrei Gherzan

sdcard_image-rpi.bbclass: Use armstub machine feature

2019-07-20T20:56:21+00:00

Signed-off-by: Andrei Gherzan

sdcard_image-rpi.bbclass: Fix typo

2019-07-20T20:56:21+00:00

Signed-off-by: Andrei Gherzan

sdcard_image-rpi.bbclass: Include in the SD card image the armstub file

2019-07-20T20:56:21+00:00

Signed-off-by: Andrei Gherzan

sdcard_image-rpi : minor bug in use of FATPAYLOAD

2019-07-20T20:56:21+00:00

Double quotation marks were added around FATPAYLOAD to prevent parsing error when FATPAYLOAD contains list of file names Signed-off-by: Nataliya Korovkina

sdcard_image-rpi: Format boot partition as FAT32

2019-02-19T13:41:28+00:00

Closes: #382 Signed-off-by: Richard Osterloh

sdcard_image-rpi.bbclass: Remove SDIMG_COMPRESSION

2018-12-12T16:23:32+00:00

Using SDIMG_COMPRESSION variable to choose compression type for produced images is deprecated. IMAGE_FSTYPES should be used instead. This patch removes any response to SDIMG_COMPRESSION within sdcard_image-rpi.bbclass Signed-off-by: Iurii Lunev

sdcard_image-rpi: fix kernel artifacts variables

2018-09-07T12:01:51+00:00

${INITRAMFS_SYMLINK_NAME} has been changed to ${INITRAMFS_LINK_NAME} in poky's commit f09947586c5c2c05368651838fea970808ab161d

sdcard_image-rpi.bbclass: allow to easily deploy vfat partition even for non u-boot case

2018-07-16T15:54:32+00:00

Signed-off-by: Martin Jansa