Google Git
Sign in
android / kernel / configs / 297de700257b1c8bcd5e61684622432b8f97121a
commit297de700257b1c8bcd5e61684622432b8f97121a[log] [tgz]
authorSteve Muckle <smuckle@google.com>Tue Nov 28 11:18:23 2017 -0800
committerSteve Muckle <smuckle@google.com>Tue Nov 28 11:18:23 2017 -0800
tree00a0365b7e805867ac89e5d9595cdff3c516eaaa
parentfb1cfddf8109a712358bfcc9096206c37e6cd39a [diff]
move CONFIG_RANDOMIZE_BASE to recommended

CONFIG_RANDOMIZE_BASE is not strictly required by Android.

Bug: 69368848
Test: run vts-kernel -m VtsKernelConfig
Change-Id: Ibc68339c453e10a7d0fec9aa29a694effa45904a
Signed-off-by: Steve Muckle <smuckle@google.com>
6 files changed
tree: 00a0365b7e805867ac89e5d9595cdff3c516eaaa
  1. android-3.18/
  2. android-4.4/
  3. android-4.9/
  4. OWNERS
  5. README.md
README.md

Android Kernel Config Fragments

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.