commit | 73ab4a29bed4183c757f329b906cb3f0e59835da | [log] [tgz] |
---|---|---|
author | Steve Muckle <smuckle@google.com> | Tue Nov 28 22:26:38 2017 +0000 |
committer | android-build-merger <android-build-merger@google.com> | Tue Nov 28 22:26:38 2017 +0000 |
tree | 00a0365b7e805867ac89e5d9595cdff3c516eaaa | |
parent | c932ff00fe8513ae5bf6bb1e39d02b36ef4f490a [diff] | |
parent | 297de700257b1c8bcd5e61684622432b8f97121a [diff] |
move CONFIG_RANDOMIZE_BASE to recommended am: 297de70025 Change-Id: Icc683dc6ee7534ae139667a517ba184fa2926f5d
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.