| commit | ea1dab85ace7577730408727204da551df430109 | [log] [tgz] |
|---|---|---|
| author | Steve Muckle <smuckle@google.com> | Thu Nov 09 11:15:41 2017 -0800 |
| committer | Steve Muckle <smuckle@google.com> | Thu Nov 09 11:15:41 2017 -0800 |
| tree | ad3d56f0683fb88a43cd60b0be924c33eb0311f6 | |
| parent | e56c1da97de7097028d2a98dc65953bbd8b19316 [diff] |
add CONFIG_SDCARD_FS to recommended Bug: 68488621 Change-Id: Icb06460ae04855f7063e62cb08b7661ea99ad39a 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.