| commit | 9b6d22407fefab62301b7e49a80f3fa154bbc2b0 | [log] [tgz] |
|---|---|---|
| author | Jerry Wong <jerry.wong@broadcom.com> | Thu Sep 03 15:06:30 2020 -0700 |
| committer | Jerry Wong <jerry.wong@broadcom.com> | Thu Sep 17 20:01:54 2020 +0000 |
| tree | 3e5d841f023bad0cce8a1f9497f662797508fbe7 | |
| parent | f65b344e69ebe936d3148cfb56d446e35e4dce17 [diff] |
P: do not mandate LMK for O/O-MR1 launches Userspace lmkd can be enabled in Android P, and therefore kernel lowmemorykiller driver should not be mandated even for devices launched prior to P. Bug: 113836751 Change-Id: I274a36010039a57211dc54bb5d3ba58ccf26e057
The files in these directories are meant to be used as a base for an Android kernel config. All devices must have the options in android-base.cfg configured as specified. If an android-base-ARCH.cfg file exists for the architecture of your device, the options in that file must be configured as specified also.
While not mandatory, the options in android-recommended.cfg enable advanced Android features.
Assuming you already have a minimalist defconfig for your device, a possible way to enable these options would be to use the merge_config.sh script in the kernel tree. From the root of the kernel tree:
ARCH=<arch> scripts/kconfig/merge_config.sh <...>/<device>_defconfig <...>/android-base.cfg <...>/android-base-<arch>.cfg <...>/android-recommended.cfg
This will generate a .config that can then be used to save a new defconfig or compile a new kernel with Android features enabled.
Because there is no tool to consistently generate these config fragments, lets keep them alphabetically sorted instead of random.