2019-02-26 15:43:27 +00:00
|
|
|
# Reference: <https://postmarketos.org/vendorkernel>
|
|
|
|
# Kernel config based on: arch/arm/configs/FRT_defconfig
|
2020-02-28 10:17:04 +00:00
|
|
|
# Maintainer: Piotr Halama <skrzynka@halamix2.pl>
|
2020-04-25 09:51:42 +00:00
|
|
|
pkgname=linux-nokia-frt
|
2019-02-26 15:43:27 +00:00
|
|
|
pkgver=3.18.79
|
*/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=3
|
2019-02-26 15:43:27 +00:00
|
|
|
pkgdesc="Nokia 1 kernel fork"
|
|
|
|
arch="armv7"
|
|
|
|
_carch="arm"
|
|
|
|
_flavor="nokia-frt"
|
|
|
|
url="https://www.nokia.com/phones/en_int/opensource/"
|
|
|
|
license="GPL-2.0-only"
|
2020-04-21 01:24:27 +00:00
|
|
|
options="!strip !check !tracedeps pmb:cross-native"
|
2020-05-02 03:37:16 +00:00
|
|
|
makedepends="perl sed installkernel bash gmp-dev bc linux-headers elfutils-dev devicepkg-dev python3"
|
2019-02-26 15:43:27 +00:00
|
|
|
|
|
|
|
# Source
|
|
|
|
_repository="android_kernel_nokia_1"
|
2019-05-26 18:07:11 +00:00
|
|
|
_commit="588ea962d4c9c21d20a7109273587e49c7da9235"
|
2020-02-28 09:59:56 +00:00
|
|
|
_config="config-$_flavor.$arch"
|
2019-02-26 15:43:27 +00:00
|
|
|
source="
|
2020-02-28 09:59:56 +00:00
|
|
|
$pkgname-$_commit.tar.gz::https://github.com/pmsourcedump/$_repository/archive/$_commit.tar.gz
|
2019-02-26 15:43:27 +00:00
|
|
|
$_config
|
|
|
|
gcc8-fix-put-user.patch
|
2019-05-26 18:07:11 +00:00
|
|
|
00_symlinks.patch
|
|
|
|
01_makefile_path.patch
|
|
|
|
02_drvgen_mk.patch
|
2019-02-26 15:43:27 +00:00
|
|
|
03_vdsomunge_upstream.patch
|
2020-05-02 03:37:16 +00:00
|
|
|
py3-compat.patch
|
2019-02-26 15:43:27 +00:00
|
|
|
"
|
2020-05-02 03:37:16 +00:00
|
|
|
|
2020-02-28 09:59:56 +00:00
|
|
|
builddir="$srcdir/$_repository-$_commit"
|
2019-02-26 15:43:27 +00:00
|
|
|
|
|
|
|
prepare() {
|
|
|
|
default_prepare
|
2020-04-01 07:09:30 +00:00
|
|
|
. downstreamkernel_prepare
|
2019-02-26 15:43:27 +00:00
|
|
|
}
|
|
|
|
|
|
|
|
build() {
|
|
|
|
unset LDFLAGS
|
|
|
|
make ARCH="$_carch" CC="${CC:-gcc}" \
|
|
|
|
KBUILD_BUILD_VERSION="$((pkgrel + 1 ))-postmarketOS"
|
|
|
|
}
|
|
|
|
|
|
|
|
package() {
|
2020-02-18 08:34:06 +00:00
|
|
|
downstreamkernel_package "$builddir" "$pkgdir" "$_carch" "$_flavor"
|
2019-02-26 15:43:27 +00:00
|
|
|
|
|
|
|
# Modules
|
|
|
|
unset LDFLAGS
|
|
|
|
make ARCH="$_carch" CC="${CC:-gcc}" \
|
|
|
|
KBUILD_BUILD_VERSION="$((pkgrel + 1))-postmarketOS" \
|
|
|
|
INSTALL_MOD_PATH="$pkgdir" INSTALL_MOD_STRIP=1 \
|
|
|
|
modules_install
|
|
|
|
}
|
|
|
|
|
2019-05-26 18:07:11 +00:00
|
|
|
sha512sums="676be1813c0886c509591a4940b9fdbd91243aaf84a8efebd7229f681e84211d86cc3466079808eb2fba45c0ada4bc7d43a4b5ab599326702c1d4830fa16d630 linux-nokia-frt-588ea962d4c9c21d20a7109273587e49c7da9235.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
|
|
|
8022a2eeb992f17119844a09ed431088001ee5c8701efe320419d9eaec5abe7bdd551183ce3b962eb241accaabb52628680c41008c33463732030c114a5813d0 config-nokia-frt.armv7
|
2019-02-26 15:43:27 +00:00
|
|
|
197d40a214ada87fcb2dfc0ae4911704b9a93354b75179cd6b4aadbb627a37ec262cf516921c84a8b1806809b70a7b440cdc8310a4a55fca5d2c0baa988e3967 gcc8-fix-put-user.patch
|
2019-05-26 18:07:11 +00:00
|
|
|
1d1a99de49b29069eb1711ad884e3f0db0956d8eeb81bdb332e6aa13fb7f5cdd48cd75791cebc08b1aa0644cdd643d7632791a272333547a6ffe68a75295e7a8 00_symlinks.patch
|
|
|
|
ef8b9da80ca67424a02acfbf99924e3ea06574c83c6a737031f6ac41b718742ef0bd66b968b14118cac021067e29184e2199f238ace2a43dc2176d9cce796bc5 01_makefile_path.patch
|
|
|
|
aaf7e208f307db3126202f3f3410d4f8a74b450ef719717a064c817258cb428a150a798494f57e43f9e1f747ad83527e565f8d81c3c746d1fb0b4e42e6e30d50 02_drvgen_mk.patch
|
2020-05-02 03:37:16 +00:00
|
|
|
19a6c3445bfd8057e4fabe1709f3d2344f3a99fef49b44636c07a18ba8791fab1bcff77f93aadff887946ae6f83c9d86e1c28f9b88d03c6ba156704d430b4470 03_vdsomunge_upstream.patch
|
|
|
|
0729fc816ea28693e7cbf4b71fc4117b124907a6a5327589e9ec2d222105c0bd0cba2320461c86b7322fc708973122bb66ca745e32cc70791225c5bbb872f999 py3-compat.patch"
|