**EDIT by @ollieparanoid, 2024-07-29:** # How to get more kernel config options enabled Kernel config checks have been reworked a lot, and the `kconfigchecks.toml` file is now in pmaports. If you would like to see kernel config options enabled, the fastest way would be to enable them yourself in a merge request. (If you feel that your proposed change is controversial, discuss it first, e.g. in postmarketos-devel. But if you feel that probably everybody benefits from this, feel free to just create the merge request.) 1. Edit `kconfigcheck.toml` and add the new options: * Extend an existing block or add a new one if it is a new topic * If you added a new block, consider adding it to the `community = [` block at the top so all devices in main and community require it. * Alternatively you may add `options="pmb:kconfigcheck-YOURNEWCATEGORY"` to specific kernels for only enforcing it there. * Example: https://gitlab.com/postmarketOS/pmaports/-/commit/a7099ed8e3e778559e36541724d9ee5382d421c5 2. Run `pmbootstrap kconfig check` to have it list the kernels that now need to be adjusted. (This no longer shows unrelated warnings, #2265!) 3. Run `pmbootstrap kconfig edit <KERNEL PACKAGE NAME>` to edit the first kernel that is failing. 4. Repeat step 2 and 3 until all kernels are adjusted. 5. Open your merge request. (It would be great if we could automate this more, with something like `pmbootstrap kconfig check --fix`, see #2190) --- **Original post from @z3ntu:** Current wishlist since it keeps growing: * CONFIG_LEDS_TRIGGER_TIMER https://gitlab.com/postmarketOS/pmaports/-/merge_requests/3335 * Wireguard + wg-quick configs (incl. https://gitlab.com/postmarketOS/pmaports/-/merge_requests/3161 and maybe https://gitlab.com/postmarketOS/pmaports/-/merge_requests/3293) * CONFIG_CRYPTO_ZSTD https://gitlab.com/postmarketOS/pmaports/-/merge_requests/3422#note_1106447232 * EXFAT * CONFIG_UINPUT for buffyboard/ttyescape * CONFIG_BTRFS_FS for btrfs support (TODO: check what other file systems we support in pmbootstrap) * Anything else?