2020-06-19 12:53:43 +00:00
|
|
|
# Reference: <https://postmarketos.org/vendorkernel>
|
|
|
|
# Kernel config based on: arch/arm64/configs/hollyss_defconfig
|
|
|
|
|
|
|
|
pkgname=linux-sony-hollyss
|
|
|
|
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
|
2020-06-19 12:53:43 +00:00
|
|
|
pkgdesc="Sony Xperia M5 kernel fork"
|
|
|
|
arch="aarch64"
|
|
|
|
_carch="arm64"
|
|
|
|
_flavor="sony-hollyss"
|
|
|
|
url="https://kernel.org"
|
|
|
|
license="GPL-2.0-only"
|
|
|
|
options="!strip !check !tracedeps pmb:cross-native"
|
|
|
|
makedepends="bash bc bison devicepkg-dev flex openssl-dev perl"
|
|
|
|
|
|
|
|
# Source
|
|
|
|
_repository="linux-sony-hollyss-kernel-3.10"
|
|
|
|
_commit="c008d85533efdc940e6052922cfeec91e582eeb2"
|
|
|
|
_config="config-$_flavor.$arch"
|
|
|
|
source="
|
|
|
|
$pkgname-$_commit.tar.gz::https://github.com/empyreal96/$_repository/archive/$_commit.tar.gz
|
|
|
|
$_config
|
|
|
|
gcc7-give-up-on-ilog2-const-optimizations.patch
|
|
|
|
gcc8-fix-put-user.patch
|
|
|
|
mt_cpufreq_64.c.patch
|
|
|
|
setup.c.patch
|
|
|
|
"
|
|
|
|
builddir="$srcdir/$_repository-$_commit"
|
|
|
|
_outdir="out"
|
|
|
|
|
|
|
|
prepare() {
|
|
|
|
default_prepare
|
|
|
|
. downstreamkernel_prepare
|
|
|
|
}
|
|
|
|
|
|
|
|
build() {
|
|
|
|
unset LDFLAGS
|
|
|
|
make O="$_outdir" ARCH="$_carch" CC="${CC:-gcc}" \
|
|
|
|
KBUILD_BUILD_VERSION="$((pkgrel + 1 ))-postmarketOS"
|
|
|
|
}
|
|
|
|
|
|
|
|
package() {
|
|
|
|
downstreamkernel_package "$builddir" "$pkgdir" "$_carch" "$_flavor" "$_outdir"
|
|
|
|
}
|
|
|
|
|
|
|
|
sha512sums="db24fa217ec5877c688e376b3bc9b8c76c59dc3bd89bdbba5a1c133c2645d0cb945c558ed83faa24f91339cf0a600f0f86da7ee4500250a63498537ec95ddab2 linux-sony-hollyss-c008d85533efdc940e6052922cfeec91e582eeb2.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
|
|
|
6623b8f1a997644e069fca0dba62af7b06e1b1e5c586693d0f5b11467b151e724f0ff19fa66b7034b14c8c0f94b35e18ecfd6c189bf427d536d2af63ff9e6fb7 config-sony-hollyss.aarch64
|
2020-06-19 12:53:43 +00:00
|
|
|
77eba606a71eafb36c32e9c5fe5e77f5e4746caac292440d9fb720763d766074a964db1c12bc76fe583c5d1a5c864219c59941f5e53adad182dbc70bf2bc14a7 gcc7-give-up-on-ilog2-const-optimizations.patch
|
|
|
|
197d40a214ada87fcb2dfc0ae4911704b9a93354b75179cd6b4aadbb627a37ec262cf516921c84a8b1806809b70a7b440cdc8310a4a55fca5d2c0baa988e3967 gcc8-fix-put-user.patch
|
|
|
|
e0ededeef62e49a36bfc27b18cb65b1d417e771e8500463dd394f5c7558571aacabac251873a8476ee1f91d7c8bf84ee6b6444f4f198e2fe7ddb310138f15e7c mt_cpufreq_64.c.patch
|
|
|
|
d290271d2133e071f2d8a2ac8c54a2e0be0b556b2faf87954ff69f15db31a9dc16a312c45d1955f7dfd227443f418242f41c3a6c88ccac43d4d43cfbcd210143 setup.c.patch"
|