commit | 7b780717faa781b6b0e84cd16cd871fa40eb11e2 | [log] [tgz] |
---|---|---|
author | Steve Muckle <smuckle@google.com> | Thu Nov 09 22:30:33 2017 +0000 |
committer | android-build-merger <android-build-merger@google.com> | Thu Nov 09 22:30:33 2017 +0000 |
tree | ad3d56f0683fb88a43cd60b0be924c33eb0311f6 | |
parent | e61eba83c900b9b7541d2fa7ca22a80d5e6d5a76 [diff] | |
parent | 2f4f1452c6fd6c8e5102bafc2f4b987bc9c3587f [diff] |
add CONFIG_SDCARD_FS to recommended am: ea1dab85ac am: 76ec18565b am: 2f4f1452c6 Change-Id: Iadd0271fed51cbecb5e0753a0295cb1193bf1219
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.