No description
Find a file
Dmitry Shmidt a7cda8fc77 android-4.14: Initial version of configs am: cfe72a2573 am: 3d26bacf36
am: f1eb25af87

Change-Id: Ida0f24912d47b7dc91b80438a3d3916b11727a91
2018-01-25 02:56:14 +00:00
android-3.18 remove CONFIG_FB requirement 2018-01-22 15:37:54 -08:00
android-4.4 remove CONFIG_FB requirement 2018-01-22 15:37:54 -08:00
android-4.9 remove CONFIG_FB requirement 2018-01-22 15:37:54 -08:00
android-4.14 android-4.14: Initial version of configs 2018-01-24 15:10:02 -08:00
OWNERS OWNERS: initial OWNERS file 2017-09-12 09:59:28 -07:00
README.md add recommended configs and README.md file 2017-09-13 16:51:44 -07:00

Android Kernel Config Fragments

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.