commit | d6b6ad1519f063d992326c68af9986d5017bf5e8 | [log] [tgz] |
---|---|---|
author | android-build-team Robot <android-build-team-robot@google.com> | Tue Nov 14 08:32:38 2017 +0000 |
committer | android-build-team Robot <android-build-team-robot@google.com> | Tue Nov 14 08:32:38 2017 +0000 |
tree | d5f4338708aff4d245704cec7ffbdc13ba87b7c5 | |
parent | 6eec14efb24dd518fa770fd1110c266e5f4374da [diff] | |
parent | 173d304a0e7cd91c6b72d8838fbcb732355f4591 [diff] |
Snap for 4450504 from 173d304a0e7cd91c6b72d8838fbcb732355f4591 to pi-release Change-Id: Ia9bf5e37214f4bbae3e18571819bce97ee9690cd
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.