Commit graph

6 commits

Author SHA1 Message Date
Clayton Craft
822e07e662
linux-*: don't use 'flavor' in kernel name (MR 2426) 2021-09-03 10:29:07 -07:00
Ignacy Kuchciński
33cbe47654
device/*/linux-*: enable CONFIG_DEVPTS_MULTIPLE_INSTANCES for <4.7 (MR 2145)
This is required for kernels earlier than 4.7 for bwrap to work for
normal users, and therefore for gnome web (epiphany) and flatpak.

[ci:skip-build] [ci:ignore-count]
2021-05-11 02:59:25 +03:00
Luca Weiss
cafeecb043
linux-fly-iq4404: don't add mtk header to zImage (MR 1483)
This is now handled by postmarketos-mkinitfs. Remove the code from the
APKBUILD.
2020-08-22 10:39:28 +02:00
Oliver Smith
0cfcc52e0d
*/linux-*: enable CONFIG_CRYPTO_XTS (MR 1405)
Enable CONFIG_CRYPTO_XTS for each kernel, so we can switch to using
aes-xts-plain64 as default cipher for cryptsetup (override with
"pmbootstrap --cipher"), instead of aes-cbc-plain64 (pmbootstrap#1940).

I have executed "pmbootstrap kconfig edit" on each kernel, and manually
toggled the option. The diff is not always clean, because for some
kernels it is apparently the first time, that menuconfig was executed on
the configs like that. In a few instances, it turned out that
CONFIG_ANDROID_PARANOID_NETWORK needed to be disabled too (this is
already a requirement, but as the config was incomplete, it was not
visible that this option was enabled). Very few times, I had to enable
CONFIG_EXPERIMENTAL in order to see and enable CONFIG_CRYPTO_XTS.

It would be great if we could automate such mass kconfig edits in the
future, see pmbootstrap#1942.

[skip ci]: I have verified, that every single one of these kernels builds.
           CI will likely run out of time while downloading source tarballs.
2020-07-11 15:26:35 +02:00
km2
bd57bf30c3
fly-iq4404: fix boot.img and kernel freezes at high disk load (MR 1285) 2020-06-07 11:01:25 +02:00
Максим
2886f1d445
fly-iq4404: new device (Fly Spark) (MR 1213) 2020-05-17 20:47:20 +03:00