2019-08-18 12:37:47 +00:00
|
|
|
# Reference: <https://postmarketos.org/vendorkernel>
|
|
|
|
|
# Kernel config based on: arch/arm/configs/wt96582_s96582aa71_defconfig
|
|
|
|
|
|
2020-04-25 09:51:42 +00:00
|
|
|
pkgname=linux-huawei-lua-u22
|
2019-08-18 12:37:47 +00:00
|
|
|
pkgver=3.10.72
|
*/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-08-18 12:37:47 +00:00
|
|
|
pkgdesc="Huawei Y3 II 3G kernel fork"
|
|
|
|
|
arch="armv7"
|
|
|
|
|
_carch="arm"
|
|
|
|
|
_flavor="huawei-lua-u22"
|
|
|
|
|
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-08-18 12:37:47 +00:00
|
|
|
makedepends="xz perl sed installkernel bash gmp-dev bc linux-headers elfutils-dev devicepkg-dev"
|
|
|
|
|
|
|
|
|
|
# Source
|
|
|
|
|
_repository="kernel-huawei-y3ii"
|
|
|
|
|
_commit="83637cb899ac81dfdabd8935181caec15a7c6929"
|
2020-02-28 09:59:56 +00:00
|
|
|
_config="config-$_flavor.$arch"
|
2019-08-18 12:37:47 +00:00
|
|
|
source="
|
2020-02-28 09:59:56 +00:00
|
|
|
$pkgname-$_commit.tar.gz::https://github.com/HenriDellal/$_repository/archive/$_commit.tar.gz
|
2019-08-18 12:37:47 +00:00
|
|
|
$_config
|
|
|
|
|
gcc7-give-up-on-ilog2-const-optimizations.patch
|
|
|
|
|
gcc8-fix-put-user.patch
|
|
|
|
|
fix-touchscreen.patch
|
|
|
|
|
kernel-use-the-gnu89-standard-explicitly.patch
|
|
|
|
|
"
|
2020-02-28 09:59:56 +00:00
|
|
|
builddir="$srcdir/$_repository-$_commit"
|
2019-08-18 12:37:47 +00:00
|
|
|
|
|
|
|
|
prepare() {
|
|
|
|
|
default_prepare
|
2020-04-01 07:09:30 +00:00
|
|
|
. downstreamkernel_prepare
|
2019-08-18 12:37:47 +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-08-18 12:37:47 +00:00
|
|
|
}
|
|
|
|
|
|
|
|
|
|
sha512sums="1772a62d28175bd31f7e1c7f5543f15ffa9a75421409f2dceff5445eaf79ded9d229538b389df0a16d3fd00c4670d625c66e4a9efc7e809fb02c8ee7b0d9a260 linux-huawei-lua-u22-83637cb899ac81dfdabd8935181caec15a7c6929.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
|
|
|
f456700958d0a3b9570ba589a767e7428d95762b1052bddc24c13ef9f1983b07c3427d7dd92e8e4a24e69849399fc53c6b824c98b5961344b5b3a88ca75abe25 config-huawei-lua-u22.armv7
|
2019-08-18 12:37:47 +00:00
|
|
|
77eba606a71eafb36c32e9c5fe5e77f5e4746caac292440d9fb720763d766074a964db1c12bc76fe583c5d1a5c864219c59941f5e53adad182dbc70bf2bc14a7 gcc7-give-up-on-ilog2-const-optimizations.patch
|
|
|
|
|
197d40a214ada87fcb2dfc0ae4911704b9a93354b75179cd6b4aadbb627a37ec262cf516921c84a8b1806809b70a7b440cdc8310a4a55fca5d2c0baa988e3967 gcc8-fix-put-user.patch
|
|
|
|
|
dd947f60b8a8082a0d4dcd9c1f0c25178d242edc18aa7ade8390d9f0b13f1756a41bf49bbe4edd890ee70d6e1d751b6d5a7fc0d6bbd4687cf1a0c3b9513a1561 fix-touchscreen.patch
|
|
|
|
|
2ec1a4d6e12dd961541f32d308b97b9daf4817976660601b38ec1ab18631ac88bef6704237f088edcc9f6508bbd4ffbb0014d1ce0fd585587267235a9658a3fe kernel-use-the-gnu89-standard-explicitly.patch"
|