forked from openkylin/platform_build
GKI: put debugging resources under fisrt_stage_ramdisk subdir.
For consistency with android-11 GKI boot-debug.img, we should put debug resources under the 'fisrt_stage_ramdisk' dir. This is needed for devices with `androidboot.force_normal_boot=1` in the kernel cmdline, where init will chroot into /fisrt_stage_ramdisk. For devices without force_normal_boot, they still can use their vendor_boot-debug.img for debugging purpose. Bug: 183670217 Test: `make bootimage_debug`, then use unpack_bootimg and `lz4 -d -c ramdisk | toybox cpio -i` to unpack the ramdisk for inspection. Change-Id: I0a79440dafd091141a1203a2c2c7be5bc1bfc836
This commit is contained in:
parent
4b2242de5e
commit
099a7c40a7
|
@ -329,7 +329,8 @@ endif
|
|||
###########################################
|
||||
# Now we can substitute with the real value of TARGET_COPY_OUT_DEBUG_RAMDISK
|
||||
ifneq (,$(filter true,$(BOARD_USES_RECOVERY_AS_BOOT) \
|
||||
$(BOARD_GKI_NONAB_COMPAT) $(BOARD_MOVE_RECOVERY_RESOURCES_TO_VENDOR_BOOT)))
|
||||
$(BOARD_GKI_NONAB_COMPAT) $(BOARD_MOVE_RECOVERY_RESOURCES_TO_VENDOR_BOOT) \
|
||||
$(BOARD_USES_GENERIC_KERNEL_IMAGE)))
|
||||
TARGET_COPY_OUT_DEBUG_RAMDISK := debug_ramdisk/first_stage_ramdisk
|
||||
TARGET_COPY_OUT_VENDOR_DEBUG_RAMDISK := vendor_debug_ramdisk/first_stage_ramdisk
|
||||
TARGET_COPY_OUT_TEST_HARNESS_RAMDISK := test_harness_ramdisk/first_stage_ramdisk
|
||||
|
|
Loading…
Reference in New Issue