2019-02-21 20:25:18 +00:00
|
|
|
# Reference: <https://postmarketos.org/vendorkernel>
|
|
|
|
|
# Kernel config based on: arch/arm64/configs/m86_user_defconfig
|
|
|
|
|
|
2020-04-25 09:51:42 +00:00
|
|
|
pkgname=linux-meizu-turbo
|
2019-02-21 20:25:18 +00:00
|
|
|
pkgver=3.10.61
|
*/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-02-21 20:25:18 +00:00
|
|
|
pkgdesc="Meizu Pro 5 kernel fork"
|
|
|
|
|
arch="aarch64"
|
|
|
|
|
_carch="arm64"
|
|
|
|
|
_flavor="meizu-turbo"
|
|
|
|
|
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-02-21 20:25:18 +00:00
|
|
|
makedepends="perl sed installkernel bash gmp-dev bc linux-headers elfutils-dev devicepkg-dev"
|
|
|
|
|
|
|
|
|
|
# Source
|
|
|
|
|
_repository="m576"
|
|
|
|
|
_commit="2d3fa1ca1fbc8b52c75b2bcc3784b7e52085768b"
|
2020-02-28 09:59:56 +00:00
|
|
|
_config="config-$_flavor.$arch"
|
2019-02-21 20:25:18 +00:00
|
|
|
source="
|
2020-02-28 09:59:56 +00:00
|
|
|
$pkgname-$_commit.tar.gz::https://github.com/meizuosc/$_repository/archive/$_commit.tar.gz
|
2019-02-21 20:25:18 +00:00
|
|
|
$_config
|
|
|
|
|
gcc7-give-up-on-ilog2-const-optimizations.patch
|
|
|
|
|
0001-Get-rid-of-Android-toolchain-binaries-in-Makefile.patch
|
|
|
|
|
0002-Make-exynos_ufs_ctrl_hci_core_clk-visible-to-other-T.patch
|
|
|
|
|
0003-Remove-hard-coded-denial-of-ro-attr-change-for-SD.patch
|
|
|
|
|
0004-Remove-loopy-symlink.patch
|
|
|
|
|
0005-Use-Samsung-MFC-from-A810.patch
|
|
|
|
|
"
|
2020-02-28 09:59:56 +00:00
|
|
|
builddir="$srcdir/$_repository-$_commit"
|
2019-02-21 20:25:18 +00:00
|
|
|
|
|
|
|
|
prepare() {
|
|
|
|
|
default_prepare
|
2020-04-01 07:09:30 +00:00
|
|
|
. downstreamkernel_prepare
|
2019-02-21 20:25:18 +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-21 20:25:18 +00:00
|
|
|
}
|
|
|
|
|
|
|
|
|
|
sha512sums="3e2fed72982aa58ae4fb403f70a0141680e01188c8c82c9272478b5fc9022de8ef7f229c44f6d07f0aa14904d6c1fb2f5fd3233440ea9f42702987ca165ce0ce linux-meizu-turbo-2d3fa1ca1fbc8b52c75b2bcc3784b7e52085768b.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
|
|
|
ca765b290e78cf74074dfec8a742625694a9d592f9213ea877469bd3b3761477f8a934ae995fc01d2875a4a7d7018d8bf3a668382a50aaf3603854d7eab98917 config-meizu-turbo.aarch64
|
2019-02-21 20:25:18 +00:00
|
|
|
77eba606a71eafb36c32e9c5fe5e77f5e4746caac292440d9fb720763d766074a964db1c12bc76fe583c5d1a5c864219c59941f5e53adad182dbc70bf2bc14a7 gcc7-give-up-on-ilog2-const-optimizations.patch
|
|
|
|
|
1ebe72fe30dc92015b518ebc6eed9145a71b6a71efecd130757013831bcc1ba75e40dce5b8708028c8604ab9737d7679fce941dd879fcddf0b290d5d02cafae9 0001-Get-rid-of-Android-toolchain-binaries-in-Makefile.patch
|
|
|
|
|
9669953f33404ebbceb91ac20c9023e76c35c5d21c2a506917139f58f16d5670ee085c366199b9a154fe4b5c6bfd59ed5a0af9fc06d7e92c2bf0b876f66e44b6 0002-Make-exynos_ufs_ctrl_hci_core_clk-visible-to-other-T.patch
|
|
|
|
|
f81ec28b6bcf59ed842ccf1fe6549d847b804a54d0e705f60c68e3cb07f776763c7ddd2168dacc1d23c4b0c6602bae84c3a921b4df7f2545ae2597c54c4dd4c1 0003-Remove-hard-coded-denial-of-ro-attr-change-for-SD.patch
|
|
|
|
|
8b43266d761e952624e477ce281ea6d6e9b4243ce149ce56487799faeb2ad58b3916b9aa6f8b905715132c20c8d55e59e1e7e3c69ad05f42e79461e181f26b23 0004-Remove-loopy-symlink.patch
|
|
|
|
|
f62c152bc7832a31d4d148d9b2f378be70f82a5ae4d32a82da52291e00cbe82dfefe72dd1383ec9a6e801d94bbf114728c8988d7cc2219beb7ae93eada886e68 0005-Use-Samsung-MFC-from-A810.patch"
|