2020-05-27 00:05:15 +00:00
|
|
|
# Maintainer: Caleb Connolly <caleb@connolly.tech>
|
|
|
|
|
# Kernel config based on: arch/arm64/configs/defconfig
|
|
|
|
|
|
|
|
|
|
_flavor="oneplus-sdm845"
|
|
|
|
|
pkgname=linux-$_flavor
|
|
|
|
|
pkgver=5.7_rc6
|
*/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
|
2020-07-11 09:16:39 +00:00
|
|
|
pkgdesc="Kernel fork for OnePlus SDM845 devices, close to mainline"
|
2020-05-27 00:05:15 +00:00
|
|
|
arch="aarch64"
|
|
|
|
|
_carch="arm64"
|
2020-07-08 18:29:12 +00:00
|
|
|
url="https://gitlab.com/sdm845-mainline/sdm845-linux"
|
2020-05-27 00:05:15 +00:00
|
|
|
license="GPL-2.0-only"
|
|
|
|
|
options="!strip !check !tracedeps pmb:cross-native"
|
|
|
|
|
makedepends="bison findutils flex installkernel openssl-dev perl"
|
|
|
|
|
|
|
|
|
|
_config="config-$_flavor.$arch"
|
2020-05-27 00:21:07 +00:00
|
|
|
_commit="d99aa17c6fd4528f0fc375b86d3390562046ba88"
|
2020-05-27 00:05:15 +00:00
|
|
|
|
|
|
|
|
# Source
|
|
|
|
|
source="
|
2020-07-08 18:29:12 +00:00
|
|
|
sdm845-linux-$_commit.tar.gz::https://gitlab.com/sdm845-mainline/sdm845-linux/-/archive/$_commit/sdm845-linux-$_commit-sdm845.tar.gz
|
2020-05-27 00:05:15 +00:00
|
|
|
$_config
|
|
|
|
|
"
|
2020-07-08 18:29:12 +00:00
|
|
|
builddir="$srcdir/sdm845-linux-$_commit"
|
2020-05-27 00:05:15 +00:00
|
|
|
|
|
|
|
|
prepare() {
|
|
|
|
|
default_prepare
|
|
|
|
|
mkdir -p "$srcdir"/build
|
|
|
|
|
cp -v "$srcdir"/$_config "$srcdir"/build/.config
|
|
|
|
|
make -C "$builddir" O="$srcdir"/build ARCH="$_carch" \
|
|
|
|
|
olddefconfig
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
build() {
|
|
|
|
|
cd "$srcdir"/build
|
|
|
|
|
unset LDFLAGS
|
|
|
|
|
make ARCH="$_carch" CC="${CC:-gcc}" \
|
|
|
|
|
KBUILD_BUILD_VERSION="$((pkgrel + 1 ))-$_flavor"
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
package() {
|
|
|
|
|
cd "$srcdir/build/arch/$_carch/boot"
|
|
|
|
|
|
|
|
|
|
install -D "$srcdir/build/include/config/kernel.release" \
|
|
|
|
|
"$pkgdir/usr/share/kernel/$_flavor/kernel.release"
|
|
|
|
|
|
|
|
|
|
cd "$srcdir"/build
|
|
|
|
|
mkdir -p "$pkgdir"/boot
|
2020-05-27 00:21:07 +00:00
|
|
|
make zinstall modules_install dtbs_install \
|
2020-05-27 00:05:15 +00:00
|
|
|
ARCH="$_carch" \
|
|
|
|
|
INSTALL_PATH="$pkgdir"/boot/ \
|
|
|
|
|
INSTALL_MOD_PATH="$pkgdir" \
|
|
|
|
|
INSTALL_DTBS_PATH="$pkgdir/usr/share/dtb"
|
|
|
|
|
}
|
|
|
|
|
|
2020-07-08 18:29:12 +00:00
|
|
|
sha512sums="cc533f97d5bf6a42f50c3487bb44286b6ebc594fe37b0818575bef6ef70a8d55ee630ba9c1534bf39159a7ec88ba7fccef4457dca2864268f6ca38400e6857a7 sdm845-linux-d99aa17c6fd4528f0fc375b86d3390562046ba88.tar.gz
|
*/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
|
|
|
02b825b64f592f56098ee4de62f1692b63d74f4f7bbd2592ec7e105b308b3a241c9a5d132fe5cfd49002bbfd3dfcba9181ea451e680713e83d64796c8c9aa308 config-oneplus-sdm845.aarch64"
|