| commit | 173d304a0e7cd91c6b72d8838fbcb732355f4591 | [log] [tgz] |
|---|---|---|
| author | Steve Muckle <smuckle@google.com> | Mon Nov 13 19:34:57 2017 +0000 |
| committer | android-build-merger <android-build-merger@google.com> | Mon Nov 13 19:34:57 2017 +0000 |
| tree | d5f4338708aff4d245704cec7ffbdc13ba87b7c5 | |
| parent | 2435919a9241c7209d42fd2ab224daad2bcbc23e [diff] | |
| parent | f6e599071190d5b6ca930eb04aab4b1bb5ac839a [diff] |
move CONFIG_RANDOMIZE_BASE out of global base config am: fb1cfddf81 am: 22a102865c am: f6e5990711 Change-Id: Ie818c97e179faabec000e229a778b72957a4c2d3
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.