| commit | 827f8c14e26702ade767d19c6dc23f2c7172583a | [log] [tgz] |
|---|---|---|
| author | Steve Muckle <smuckle@google.com> | Tue May 22 13:15:49 2018 -0700 |
| committer | Steve Muckle <smuckle@google.com> | Tue May 29 11:42:48 2018 -0700 |
| tree | a629bbcece78882b7c840bc3304f2d77ab460cde | |
| parent | e97c5487372cb8e73e77c4f63d3011c90580dbdd [diff] |
remove 3.18 kernel config fragments The 3.18 kernel is no longer supported for device launches. Change-Id: Iec4eef01408a5f52780553029c5f6732498ccdc8 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.