commit | bff67d412b50eaad14acac85cd3ab5209a68ea71 | [log] [tgz] |
---|---|---|
author | android-build-team Robot <android-build-team-robot@google.com> | Wed Apr 18 07:24:50 2018 +0000 |
committer | android-build-team Robot <android-build-team-robot@google.com> | Wed Apr 18 07:24:50 2018 +0000 |
tree | 59e4ddc8a714bb95801caef6dd732daba11684f1 | |
parent | abc98ef212938d2a47adda69bac46f4625fce757 [diff] | |
parent | ff3317b3c84379275313cf81bafa83b9f57fa875 [diff] |
Snap for 4728508 from ff3317b3c84379275313cf81bafa83b9f57fa875 to pi-release Change-Id: Icabb4b17b0b371d7acfea6e2c4259f0cfb83ac9e
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.