Google Git
Sign in
android / kernel / configs / dc6efcb26c2e5c5fed8757b6cce2020bc0b093be
commitdc6efcb26c2e5c5fed8757b6cce2020bc0b093be[log] [tgz]
authorSteve Muckle <smuckle@google.com>Tue May 29 15:33:58 2018 -0700
committerSteve Muckle <smuckle@google.com>Tue May 29 15:33:58 2018 -0700
tree2fe441bec0486af008b0c48e09e3c1fa38af8a1f
parentb583c805ea73a27e597373a0dc99ea26a8ea680a [diff]
update OWNERS file

Clean up/extend OWNERS permissions.

Change-Id: Icd051817662fdcfad352d35c18543a82ac24b159
Signed-off-by: Steve Muckle <smuckle@google.com>
1 file changed
tree: 2fe441bec0486af008b0c48e09e3c1fa38af8a1f
  1. android-4.14/
  2. android-4.4/
  3. android-4.9/
  4. o/
  5. o-mr1/
  6. p/
  7. OWNERS
  8. 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.