commit | e446c5c1abdd8b3015e0b880d51bcfb616159d49 | [log] [tgz] |
---|---|---|
author | Steve Muckle <smuckle@google.com> | Tue Jan 23 02:43:11 2018 +0000 |
committer | android-build-merger <android-build-merger@google.com> | Tue Jan 23 02:43:11 2018 +0000 |
tree | 5665be8b1f5a9532b7bc49faa32ec6bcc4d6e3ef | |
parent | 62b1c76efffa4752c4f441df8165eecd8d8cef15 [diff] | |
parent | ded6b937c7bba75037583e81a4019fab14ab2218 [diff] |
remove CONFIG_FB requirement am: 92e529f313 am: ec44bff68a am: ded6b937c7 Change-Id: I425016b48a0927e8dc0da8f35a21b6156fbb85b0
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.