2019-12-03 17:23:00 +00:00
|
|
|
# Maintainer: Alexey Min <alexey.min@gmail.com>
|
|
|
|
|
# Kernel config based on: arch/arm64/configs/defconfig
|
|
|
|
|
|
|
|
|
|
_flavor="postmarketos-qcom-sdm660"
|
2020-04-25 09:51:42 +00:00
|
|
|
pkgname=linux-$_flavor
|
2019-12-03 17:23:00 +00:00
|
|
|
pkgver=5.6_rc1
|
*/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 13:24:19 +00:00
|
|
|
pkgrel=1
|
2019-12-03 17:23:00 +00:00
|
|
|
pkgdesc="QCOM group's fork of mainline linux"
|
|
|
|
|
arch="aarch64" # sdm660 is arm64 only
|
|
|
|
|
url="https://kernel.org/"
|
|
|
|
|
license="GPL-2.0-only"
|
2020-04-21 01:24:27 +00:00
|
|
|
options="!strip !check !tracedeps pmb:cross-native"
|
2019-12-03 17:23:00 +00:00
|
|
|
makedepends="bison findutils flex installkernel openssl-dev perl"
|
|
|
|
|
|
|
|
|
|
_repo="linux-postmarketos"
|
|
|
|
|
_commit="8dc3769c8a680bfc1f38221e68d3fd994f490970"
|
|
|
|
|
|
|
|
|
|
source="
|
|
|
|
|
$_repo-$_commit.tar.bz2::https://gitlab.com/postmarketOS/$_repo/-/archive/$_commit/$_repo-$_commit.tar.bz2
|
|
|
|
|
config-$_flavor.aarch64
|
|
|
|
|
0001-arm64-dts-qcom-Add-sdm630-sdm660-SoC-and-xiaomi-lave.patch
|
|
|
|
|
"
|
|
|
|
|
|
|
|
|
|
_carch="arm64"
|
|
|
|
|
|
|
|
|
|
builddir="$srcdir/$_repo-$_commit"
|
|
|
|
|
|
|
|
|
|
prepare() {
|
|
|
|
|
default_prepare
|
|
|
|
|
cp -v "$srcdir/config-$_flavor.$CARCH" "$builddir"/.config
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
build() {
|
|
|
|
|
unset LDFLAGS
|
|
|
|
|
make ARCH="$_carch" CC="${CC:-gcc}" \
|
|
|
|
|
KBUILD_BUILD_VERSION="$((pkgrel + 1 ))-$_flavor"
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
package() {
|
|
|
|
|
# bootloader requires compressed kernel
|
|
|
|
|
install -Dm644 "$builddir/arch/$_carch/boot/Image.gz" \
|
|
|
|
|
"$pkgdir/boot/vmlinuz-$_flavor"
|
|
|
|
|
|
|
|
|
|
install -D "$builddir/include/config/kernel.release" \
|
|
|
|
|
"$pkgdir/usr/share/kernel/$_flavor/kernel.release"
|
|
|
|
|
|
|
|
|
|
make modules_install dtbs_install \
|
|
|
|
|
ARCH="$_carch" \
|
|
|
|
|
INSTALL_MOD_PATH="$pkgdir" \
|
|
|
|
|
INSTALL_DTBS_PATH="$pkgdir/usr/share/dtb"
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
sha512sums="b53b17709eea1b8cd8fc9158762f0e2fefad7baa383dbee2ba758e9aed89cf411b2bd65386823821b877ced5f0b525f5ddc67cd048fddf47c9104eea42ab81f0 linux-postmarketos-8dc3769c8a680bfc1f38221e68d3fd994f490970.tar.bz2
|
*/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 13:24:19 +00:00
|
|
|
dd51522254d69e339dba74f575accf8d62b2c593b2e8d52e60aa6e9856da631a8430bff954f262ab30d6172806003448c0030f549180ff6001fd9ef7e5a126c5 config-postmarketos-qcom-sdm660.aarch64
|
2019-12-03 17:23:00 +00:00
|
|
|
a5c4036e916716a66277c40d2adfc526401c7abdfe5222e237deb585bd4081cb36023696e794e0531413caf1296b88072f3506086dee99e1388e2874d72880bc 0001-arm64-dts-qcom-Add-sdm630-sdm660-SoC-and-xiaomi-lave.patch"
|