commit | 9bbb4c3dab0545c95d26f0f67230ba1d280a81c0 | [log] [tgz] |
---|---|---|
author | Hridya Valsaraju <hridya@google.com> | Mon Apr 16 15:32:11 2018 -0700 |
committer | Hridya Valsaraju <hridya@google.com> | Wed Apr 18 11:25:27 2018 -0700 |
tree | 8d40e89ab370ae0db9040c1f6851cd3a57afea83 | |
parent | 432aff48e24c3c279aaf07c318ad83503f3c4f89 [diff] |
Require CONFIG_DETECT_HUNG_TASK Bug: 77842593 Test: run vts-kernel -m VtsKernelConfig Change-Id: I8c374154cefc9150f35297863dd453c668e8b844
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.