commit | 5ecbb222d67eda97c6ac21c5bcf256bebb972301 | [log] [tgz] |
---|---|---|
author | Steve Muckle <smuckle@google.com> | Fri Feb 16 19:44:41 2018 +0000 |
committer | android-build-merger <android-build-merger@google.com> | Fri Feb 16 19:44:41 2018 +0000 |
tree | 1f358f0f1afc5e002607acc22f025cb8c68d10d3 | |
parent | f1eb25af873c854950f0e012ccf594f90da8964d [diff] | |
parent | 4ddffe688a36216841c9efba4fd725d925d273c6 [diff] |
android-4.4: restore restriction on CONFIG_INET_LRO am: c248a95d1c am: 4ddffe688a Change-Id: I290e70eaa3df59631f552a64141435b44e6c8fb8
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.