community kconfig check: add more options
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.)
- 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: a7099ed8
- Run
pmbootstrap kconfig check
to have it list the kernels that now need to be adjusted. (This no longer shows unrelated warnings, pmbootstrap#2265 (closed)!) - Run
pmbootstrap kconfig edit <KERNEL PACKAGE NAME>
to edit the first kernel that is failing. - Repeat step 2 and 3 until all kernels are adjusted.
- Open your merge request.
(It would be great if we could automate this more, with something like pmbootstrap kconfig check --fix
, see pmbootstrap#2190)
Original post from @z3ntu:
Current wishlist since it keeps growing:
- CONFIG_LEDS_TRIGGER_TIMER !3335 (closed)
- Wireguard + wg-quick configs (incl. !3161 (closed) and maybe !3293 (closed))
- CONFIG_CRYPTO_ZSTD !3422 (comment 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?
Edited by Administrator