diff options
| author | 2021-07-29 23:35:33 +0800 | |
|---|---|---|
| committer | 2021-07-30 00:54:47 +0000 | |
| commit | 87f60017b964997e877c8c322f6228c08dcb81ff (patch) | |
| tree | 0dd6dc362ff6a8cb69fd9ee926b4a86d2ed52ff8 /tools/warn/cpp_warn_patterns.py | |
| parent | 6c4e8d5f975c980ca8de72a19d4273663c331137 (diff) | |
Adding vendor_boot-test-harness.img
boot-test-harness.img is used to allow adb root on user build
images. It also sets properties: ro.audio.silent=1 & ro.test_harness=1.
GKI 2.0 devices will use BOARD_PREBUILT_BOOTIMAGE so
boot-test-harness.img will not be generated.
Therefore, we have to introduce the vendor_boot-test-harness.img
as an alternative for boot-test-harness.img.
In the future, we'll simplify the flow as:
+ If a device has a /vendor_boot partition, builds
vendor_boot-(test-harness|debug).img.
+ Otherwise, builds boot-(test-harness|debug).img.
boot-(test-harness|debug).img needs to be kept for some clients
to gracefully transit to using vendor_boot-(test-harness|debug).img.
Bug: 194654549
Test: make then `unpack_bootimg --boot_img $OUT/vendor_boot-test-harness.img`
Test: Check the ramdisk content in ./out/vendor_ramdisk
Change-Id: If3a1393b4ff3e69bb9b62f3b843b7858437d47bf
Diffstat (limited to 'tools/warn/cpp_warn_patterns.py')
0 files changed, 0 insertions, 0 deletions