commit | 059ca1589c0b1470b9b74bfa873cb48b9829f704 | [log] [tgz] |
---|---|---|
author | Steve Muckle <smuckle@google.com> | Fri Sep 15 18:59:42 2017 +0000 |
committer | android-build-merger <android-build-merger@google.com> | Fri Sep 15 18:59:42 2017 +0000 |
tree | 2b329c65f1a7f4cd71089cd9ea63736bbd4f3cc4 | |
parent | 36784bac45f59f1e7d790396cadd60f018bc6625 [diff] | |
parent | c992cecdfc0b921604fd7b71eb0c511a7fcb1189 [diff] |
add recommended configs and README.md file am: 649be155f9 am: 1a1cab16da am: c992cecdfc Change-Id: If9b036497fefad779f5633a822ed5ecff16ea335
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.