tag | ad66047096024d413e94f18ee22c7e15fd8ff77f | |
---|---|---|
tagger | The Android Open Source Project <initial-contribution@android.com> | Tue Jun 26 09:56:21 2018 -0700 |
object | d134f765906a6f8bcdf51863a55b0495c78df8a7 |
Android p preview 4
commit | d134f765906a6f8bcdf51863a55b0495c78df8a7 | [log] [tgz] |
---|---|---|
author | Steve Muckle <smuckle@google.com> | Tue Jun 05 13:33:36 2018 -0700 |
committer | Steve Muckle <smuckle@google.com> | Tue Jun 05 16:08:50 2018 -0700 |
tree | eab3e8029ebda5f802280441ad925a99ca9faf11 | |
parent | dc6efcb26c2e5c5fed8757b6cce2020bc0b093be [diff] |
sync requirements for O, O-MR1 with VTS Bug: 109743015 Bug: 109698052 Change-Id: I99ab9ddb44d3e48d0472511a80dd9ba3ffbf95f8 Merged-In: I99ab9ddb44d3e48d0472511a80dd9ba3ffbf95f8 Signed-off-by: Steve Muckle <smuckle@google.com>
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.