| commit | cf0414b6c15afea77724890427b7ff7ebdfbae91 | [log] [tgz] |
|---|---|---|
| author | Steve Muckle <smuckle@google.com> | Sun Apr 29 14:22:51 2018 -0700 |
| committer | Steve Muckle <smuckle@google.com> | Sun Apr 29 14:22:51 2018 -0700 |
| tree | cbd507c4dfff5cdc65c7e93f35f6bf2aa508166a | |
| parent | b44db5b11b2a75a5b100e8e9ed194b8f9215b268 [diff] |
copy P kernel config requirements to p/ Copy the P kernel config requirements from the top level to p/. Bug: 78576469 Change-Id: If5e38851c793362ecc30f35bbcaf2ab502e9f999 Signed-off-by: Steve Muckle <smuckle@google.com>
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.