2020-02-16 18:49:36 +00:00
|
|
|
# Kernel config based on: arch/arm/configs/lineage_zeal_defconfig
|
|
|
|
|
|
2020-04-25 09:51:42 +00:00
|
|
|
pkgname=linux-nokia-rm846
|
2020-02-16 18:49:36 +00:00
|
|
|
pkgver=3.4.0
|
*/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-02-16 18:49:36 +00:00
|
|
|
pkgdesc="Lumia 620 kernel fork"
|
|
|
|
|
arch="armv7"
|
|
|
|
|
_carch="arm"
|
|
|
|
|
_flavor="nokia-rm846"
|
|
|
|
|
url="https://kernel.org"
|
|
|
|
|
license="GPL2"
|
2020-04-21 01:24:27 +00:00
|
|
|
options="!strip !check !tracedeps pmb:cross-native"
|
2020-02-16 18:49:36 +00:00
|
|
|
makedepends="perl sed installkernel bash gmp-dev bc linux-headers elfutils-dev devicepkg-dev gcc6"
|
|
|
|
|
|
|
|
|
|
# Compiler: GCC 6 (doesn't boot when compiled with newer versions)
|
|
|
|
|
if [ "${CC:0:5}" != "gcc6-" ]; then
|
|
|
|
|
CC="gcc6-$CC"
|
|
|
|
|
HOSTCC="gcc6-gcc"
|
|
|
|
|
CROSS_COMPILE="gcc6-$CROSS_COMPILE"
|
|
|
|
|
fi
|
|
|
|
|
|
|
|
|
|
# Source
|
|
|
|
|
_repository="android_kernel_nokia_msm8x27"
|
|
|
|
|
_commit="28fe134696ce748ddaaf3633d3e345d3509276bd"
|
|
|
|
|
_config="config-$_flavor.$arch"
|
|
|
|
|
source="
|
|
|
|
|
$pkgname-$_commit.tar.gz::https://github.com/Android4Lumia/android_kernel_nokia_msm8x27/archive/$_commit.tar.gz
|
|
|
|
|
$_config
|
|
|
|
|
00_fix_return_address.patch
|
|
|
|
|
psmouse_base.patch
|
|
|
|
|
02_gpu-msm-fix-gcc5-compile.patch
|
|
|
|
|
"
|
|
|
|
|
builddir="$srcdir/$_repository-$_commit"
|
|
|
|
|
|
|
|
|
|
prepare() {
|
|
|
|
|
default_prepare
|
2020-04-01 07:09:30 +00:00
|
|
|
. downstreamkernel_prepare
|
2020-02-16 18:49:36 +00:00
|
|
|
}
|
|
|
|
|
|
|
|
|
|
build() {
|
|
|
|
|
unset LDFLAGS
|
|
|
|
|
make ARCH="$_carch" CC="${CC:-gcc}" \
|
|
|
|
|
KBUILD_BUILD_VERSION="$((pkgrel + 1 ))-postmarketOS"
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
package() {
|
|
|
|
|
# kernel.release
|
|
|
|
|
install -D "$builddir/include/config/kernel.release" \
|
|
|
|
|
"$pkgdir/usr/share/kernel/$_flavor/kernel.release"
|
|
|
|
|
|
|
|
|
|
# zImage (find the right one)
|
|
|
|
|
cd "$builddir/arch/$_carch/boot"
|
|
|
|
|
_target="$pkgdir/boot/vmlinuz-$_flavor"
|
|
|
|
|
for _zimg in zImage-dtb Image.gz-dtb *zImage Image; do
|
|
|
|
|
[ -e "$_zimg" ] || continue
|
|
|
|
|
msg "zImage found: $_zimg"
|
|
|
|
|
install -Dm644 "$_zimg" "$_target"
|
|
|
|
|
break
|
|
|
|
|
done
|
|
|
|
|
if ! [ -e "$_target" ]; then
|
|
|
|
|
error "Could not find zImage in $PWD!"
|
|
|
|
|
return 1
|
|
|
|
|
fi
|
|
|
|
|
}
|
|
|
|
|
sha512sums="6a576c9bfb645083d1d8477daae647ee44f15732414cb73a585d1c7e27c5481ccdcd98d6e8fe100b61400f1c3186a3339c2d438fb605177e1d11832e93dbc70b linux-nokia-rm846-28fe134696ce748ddaaf3633d3e345d3509276bd.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
|
|
|
b7c78f1dceb17235b89ee002f87a69c2e77b8160767aef46bf4b8cce992b598cc0169b6e39b947e73d81ac7b76c20996e1e9ba176e5e87c0fc834ab9f80b78e3 config-nokia-rm846.armv7
|
2020-02-16 18:49:36 +00:00
|
|
|
ea1d3b5a234fa565e3c1a792de48f4fc4e6023d281d303c8e319c7ef28edc5739ab0e4dea0139a41f0a5c7d03e27921ccaa214fd0ac5c72245a094ce60128864 00_fix_return_address.patch
|
|
|
|
|
f7e31cfe422696922aec52002e56c58103183966edee3bb8e1995d33f8d37b07c32280a8ecc213874e358a6ff367418556a4542fba7e3c17e4b8e82e05c3a543 psmouse_base.patch
|
|
|
|
|
7be03a9e78b7ac330a54b1f00509caa0621a95c0c55901878ad757f9dd69cc05ba2c8b5ea987063ae1224f92c4d090d515fa5d369e7755181a4871b0d0f82881 02_gpu-msm-fix-gcc5-compile.patch"
|