[ti-android-12] device: don't use compression for virtual_ab_ota
When booting on the _b slot after applying an OTA, we observe boot errors such as:
[ 3.417938] init: Created socket '/dev/socket/snapuserd', mode 660, user 1000, group 1000
[ 3.427810] init: Relaunched snapuserd with pid: 106
[ 3.428303] init: Cannot launch snapuserd; execv failed: No such file or directory
[ 3.432895] init: Creating logical partitions with snapshots as needed
[ 3.449701] random: init: uninitialized urandom read (16 bytes read)
[ 3.457566] init: [libfs_mgr]Created logical partition system_b-base on device /dev/block/dm-0
[ 3.467001] random: init: uninitialized urandom read (16 bytes read)
[ 3.472311] mmc1: new high speed SDHC card at address 0001
[ 3.474657] init: Mapped COW device for system_b at /dev/block/dm-1
[ 3.479608] mmcblk1: mmc1:0001 SD16G 7.44 GiB
[ 3.490511] random: init: uninitialized urandom read (16 bytes read)
[ 3.491968] mmcblk1: p1 p2
[ 3.498167] init: [libfs_mgr]Created logical partition system_b-src on device /dev/block/dm-2
[ 13.520196] init: Timed out connecting to snapuserd socket: snapuserd
[ 13.526704] init: Unable to connect to snapuserd
[ 13.531336] init: Could not map dm-user device for partition system_b
[ 13.597747] init: Failed to mount required partitions early ...compression.mk will itself inherit from launch_with_vendor_ramdisk.mk
To quote launch_with_vendor_ramdisk:
Devices launching with Virtual A/B and has a vendor_boot partition is preferred to inherit from this makefile instead of launch.mk.
We don't have a vendor_boot partition, because this is for boot image v3, which is not supported in our current bootloader (U-Boot 2021.01-g6bf760268e)
Disable virtual_ab_ota compression to solve this while we migrate to boot image v3/v4.
Signed-off-by: Mattijs Korpershoek mkorpershoek@baylibre.com
This was reported in e2e here:
Edited by Mattijs Korpershoek