|
Name |
|
Date |
Size |
#Lines |
LOC |
| .. | | - | - |
| o/ | | 22-Nov-2023 | - | 498 | 490 |
| o-mr1/ | | 22-Nov-2023 | - | 505 | 497 |
| p/ | | 22-Nov-2023 | - | 1,031 | 1,017 |
| .git | D | 01-Jan-1970 | 0 | | |
| OWNERS | D | 22-Nov-2023 | 74 | 5 | 4 |
| README.md | D | 22-Nov-2023 | 1.1 KiB | 24 | 17 |
README.md
1# Android Kernel Config Fragments
2
3The files in these directories are meant to be used as a base for an Android
4kernel config. All devices must have the options in `android-base.cfg` configured
5as specified. If an `android-base-ARCH.cfg` file exists for the architecture of
6your device, the options in that file must be configured as specified also.
7
8While not mandatory, the options in `android-recommended.cfg` enable advanced
9Android features.
10
11Assuming you already have a minimalist defconfig for your device, a possible
12way to enable these options would be to use the `merge_config.sh` script in the
13kernel tree. From the root of the kernel tree:
14
15```sh
16 ARCH=<arch> scripts/kconfig/merge_config.sh <...>/<device>_defconfig <...>/android-base.cfg <...>/android-base-<arch>.cfg <...>/android-recommended.cfg
17```
18
19This will generate a `.config` that can then be used to save a new defconfig or
20compile a new kernel with Android features enabled.
21
22Because there is no tool to consistently generate these config fragments,
23lets keep them alphabetically sorted instead of random.
24