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
This commit is contained in:
Chris Renshaw authored and GitHub committed 2022-10-19 23:19:09 -03:00
1 parent 042d0ccf6d
commit cf1a93136c
1 file changed
+5 -4
+5 -4
View File
@@ -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