2019-04-07 03:15:50 +00:00
|
|
|
# Reference: <https://postmarketos.org/vendorkernel>
|
|
|
|
|
# Kernel config based on: arch/arm/configs/cyanogenmod_m7_defconfig
|
|
|
|
|
|
2020-04-25 09:51:42 +00:00
|
|
|
pkgname=linux-htc-m7
|
2019-04-07 03:15:50 +00:00
|
|
|
pkgver=3.4.10
|
*/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-04-07 03:15:50 +00:00
|
|
|
pkgdesc="HTC One M7 kernel fork"
|
|
|
|
|
arch="armv7"
|
|
|
|
|
_carch="arm"
|
|
|
|
|
_flavor="htc-m7"
|
|
|
|
|
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-04-07 03:15:50 +00:00
|
|
|
makedepends="perl sed installkernel bash gmp-dev bc linux-headers elfutils-dev devicepkg-dev"
|
|
|
|
|
|
|
|
|
|
# Source
|
|
|
|
|
_repository="android_kernel_htc_m7"
|
|
|
|
|
_commit="f6eb6496406f5a06cdd4716e494082d78df70e83"
|
2020-02-28 09:59:56 +00:00
|
|
|
_config="config-$_flavor.$arch"
|
2019-04-07 03:15:50 +00:00
|
|
|
source="
|
2020-02-28 09:59:56 +00:00
|
|
|
$pkgname-$_commit.tar.gz::https://github.com/LineageOS/$_repository/archive/$_commit.tar.gz
|
2019-04-07 03:15:50 +00:00
|
|
|
$_config
|
|
|
|
|
0001-don-t-hardcode-cross_compile-in-makefile.patch
|
|
|
|
|
0002-change-lzop-9-to-lzop-6.patch
|
|
|
|
|
gcc8-fix-put-user.patch
|
|
|
|
|
kernel-use-the-gnu89-standard-explicitly.patch
|
|
|
|
|
"
|
2020-02-28 09:59:56 +00:00
|
|
|
builddir="$srcdir/$_repository-$_commit"
|
2019-04-07 03:15:50 +00:00
|
|
|
|
|
|
|
|
prepare() {
|
|
|
|
|
default_prepare
|
2020-04-01 07:09:30 +00:00
|
|
|
. downstreamkernel_prepare
|
2019-04-07 03:15:50 +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-04-07 03:15:50 +00:00
|
|
|
}
|
|
|
|
|
|
|
|
|
|
sha512sums="7014029604b8c448c7d2d6302b9404521d89b12a3df687f3aee10e73cd49b3c31fbd5a3db92c082eeda93e0e83b00487d0ee5e6311f4f9fcb32a4eb139d0d231 linux-htc-m7-f6eb6496406f5a06cdd4716e494082d78df70e83.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
|
|
|
117651c27454c2f3d89392acf036405ba6573e072630d56601da0d96f44b5381413dd0a0355829dba8d35c9223b7af740cda857021706cdba52ca52b02e90848 config-htc-m7.armv7
|
2019-04-07 03:15:50 +00:00
|
|
|
129e844aadc30b214ed41968b8a0246d21b224b3e7eecc8b056ec6cef122eb5dbdba3927d5db1499e7335211b74f8b38bf756fa48f099a87921e260d99eb27bc 0001-don-t-hardcode-cross_compile-in-makefile.patch
|
|
|
|
|
526bf8554203b2cde43ccb145589f8f0114f06bbc335b8eb606ec1bb1849824f087cf362bf5ea4f0b84e660de5648fe753995a109ade7aaa11f2bf7ca48d233f 0002-change-lzop-9-to-lzop-6.patch
|
|
|
|
|
197d40a214ada87fcb2dfc0ae4911704b9a93354b75179cd6b4aadbb627a37ec262cf516921c84a8b1806809b70a7b440cdc8310a4a55fca5d2c0baa988e3967 gcc8-fix-put-user.patch
|
|
|
|
|
ad0182a483791fc88e058838bc331b2f04a75ba291e763767babdb815efadfc3b4fda97e69e2e3f00a426cabea088e35297a92bd287592597d1e309be68ee92c kernel-use-the-gnu89-standard-explicitly.patch"
|