commit | df77754974e136b948b34deb53ed912e5ebf7ffe | [log] [tgz] |
---|---|---|
author | TreeHugger Robot <treehugger-gerrit@google.com> | Wed Apr 25 21:25:40 2018 +0000 |
committer | Android (Google) Code Review <android-gerrit@google.com> | Wed Apr 25 21:25:40 2018 +0000 |
tree | c83a64aa997cb195c8321cdb1101407ad8b94079 | |
parent | 41d7681eb021ad66fbd9eb7c7e85d4d7a9259dc4 [diff] | |
parent | 640db4d4e2a3ecfeb23253a511f9a0841481028c [diff] |
Merge "recommend CONFIG_REFCOUNT_FULL for 4.14" into pi-dev
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.