| commit | 4f1e1a924a28e03659180bc3009081c9d7a2aa4e | [log] [tgz] |
|---|---|---|
| author | android-build-team Robot <android-build-team-robot@google.com> | Tue May 22 07:25:05 2018 +0000 |
| committer | android-build-team Robot <android-build-team-robot@google.com> | Tue May 22 07:25:05 2018 +0000 |
| tree | 3025ecd35442594ae6667923cf2ceeb8038214d5 | |
| parent | 15302f63a8a16d6f01af5227181be03aebb3de08 [diff] | |
| parent | d546dcbe8e9b10511bf32519fe2a57face7de182 [diff] |
Snap for 4796401 from d546dcbe8e9b10511bf32519fe2a57face7de182 to pi-release Change-Id: Ib808929f641e83160a7bb0805508653eb9ecc282
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.