Add kernel requirements for target FCM 1 and 2

These requirements are restored as they were in
O tree and O-MR1 tree, respectively. Kernel
requirements should not be added retroactively.

Test: builds
Test: inspect built matrix for older devices
Bug: 78576469

P changes includes the following. This change restores
the requirement for legacy devices.

Change-Id: I950942dc31545778562bde728ab8b3c86df9fc1b
14 files changed
tree: 58ae0f2f345ab31f34968ac69ed1354556ac61a7
  1. android-3.18/
  2. android-4.14/
  3. android-4.4/
  4. android-4.9/
  5. o/
  6. o-mr1/
  7. OWNERS
  8. README.md
README.md

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.