commit | ca3b60361256cc97d839b2e235f78cc2f45d52d8 | [log] [tgz] |
---|---|---|
author | SzuWei Lin <szuweilin@google.com> | Tue Nov 08 01:08:58 2022 +0000 |
committer | Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com> | Tue Nov 08 01:08:58 2022 +0000 |
tree | a89d66a3f0b36b902084111a7a3796e4ec477438 | |
parent | 31f94b53210194e6a4f5d694a7ed38b76b75092d [diff] | |
parent | 7572416973dfa36236ddd2c73395315aad8ef5d5 [diff] |
Merge "Add content about support system_dlkm partition" am: 7572416973 Original change: https://android-review.googlesource.com/c/device/generic/common/+/2286974 Change-Id: I38e37dc3c6247abe50c35a7ef392358d853ea2a8 Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
This document introduces special GSI settings for facilitating xTS-on-GSI with a single image.
[BoardConfigGsiCommon.mk] BOARD_USES_SYSTEM_DLKMIMAGE := true BOARD_SYSTEM_DLKMIMAGE_FILE_SYSTEM_TYPE := ext4 TARGET_COPY_OUT_SYSTEM_DLKM := system_dlkm [gsi_release.mk] PRODUCT_BUILD_SYSTEM_DLKM_IMAGE := false
Starting from Android 13, all devices must include a system_dlkm partition. GSI enables system_dlkm to support the devices with system_dlkm partition, and be compatible with old devices without a system_dlkm partition.
With these configurations, /system/system_dlkm
would not be created. Instead, a /system/lib/modules
-> /system_dlkm/lib/modules
symlink is created.
For device without system_dlkm partition, the symlink would be dangling. The dangling symlink shouldn‘t be followed anyway because the device doesn’t use system_dlkm.
For device with system_dlkm, they can load modules via that path normally like when they are using their original system image.
Some devices access the private android framework resource by @*android:
while overlaying their SystemUI setting status_bar_header_height_keyguard
. However, referencing private framework resource IDs from RRO packages in the vendor partition crashes on these devices when GSI is used. This is because private framework resource don't have a stable ID, and these vendor RRO packages would be referencing to dangling resource references after GSI is used (b/245806899).
In order to prevent SystemUI crash, GSI adds a runtime resource overlay in the system_ext partition, which have higher overlay precedence than RROs on vendor partition, so the problematic vendor RROs would be overridden.
Lifetime of this package: