From cf1a93136c74a45183bfbaba5860bf766b83a9b5 Mon Sep 17 00:00:00 2001 From: Chris Renshaw Date: Wed, 19 Oct 2022 23:19:09 -0300 Subject: [PATCH] AK3: separate init_boot and boot partition detections - both boot for kernel and init_boot for first stage ramdisk access to overlay.d will be needed - remove ramdisk and recovery_ramdisk from detection since devices which use them also use kernel partition and would need to be multi-partition setups either way --- tools/ak3-core.sh | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/tools/ak3-core.sh b/tools/ak3-core.sh index 89ac43b..b8d3678 100755 --- a/tools/ak3-core.sh +++ b/tools/ak3-core.sh @@ -809,15 +809,16 @@ setup_ak() { touch $blockfiles/current; fi; - # target block partition detection enabled by block=boot recovery or auto (from anykernel.sh) + # target block partition detection enabled by block=boot recovery init_boot vendor_boot or auto (from anykernel.sh) case $block in auto|"") block=boot;; esac; case $block in - boot|recovery|vendor_boot) + boot|recovery|init_boot|vendor_boot) case $block in - boot) parttype="ramdisk init_boot boot BOOT LNX android_boot bootimg KERN-A kernel KERNEL";; - recovery) parttype="ramdisk_recovery recovery RECOVERY SOS android_recovery";; + boot) parttype="boot BOOT LNX android_boot bootimg KERN-A kernel KERNEL";; + recovery) parttype="recovery RECOVERY SOS android_recovery";; + init_boot) parttype="init_boot";; vendor_boot) parttype="vendor_boot";; esac; for name in $parttype; do