2017-11-05 20:10:19 +00:00
|
|
|
# Kernel config based on: arch/arm/configs/lineageos_d2_defconfig
|
|
|
|
|
# Changes:
|
|
|
|
|
# - Added DEVTEMPFS
|
|
|
|
|
# - Enabled SYSVIPC
|
|
|
|
|
# - Disabled ANDROID_PARANOID_NETWORK
|
|
|
|
|
# Patches:
|
|
|
|
|
# - All simply to allow it to compile under GCC6.
|
|
|
|
|
|
2020-04-25 09:51:42 +00:00
|
|
|
pkgname=linux-samsung-i747m
|
2017-11-05 20:10:19 +00:00
|
|
|
pkgver=3.4.112
|
*/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
|
2017-11-05 20:10:19 +00:00
|
|
|
pkgdesc="Samsung Galaxy SIII (USA/Canada) kernel fork"
|
|
|
|
|
arch="armhf"
|
|
|
|
|
_carch="arm"
|
|
|
|
|
_flavor="samsung-i747m"
|
|
|
|
|
url="https://kernel.org"
|
|
|
|
|
license="GPL2"
|
2020-04-21 01:24:27 +00:00
|
|
|
options="!strip !check !tracedeps pmb:cross-native"
|
2020-02-18 08:34:06 +00:00
|
|
|
makedepends="perl sed installkernel bash gmp-dev bc linux-headers elfutils-dev devicepkg-dev xz gcc6"
|
2018-10-01 06:44:18 +00:00
|
|
|
|
|
|
|
|
# Compiler: this kernel was only tested with GCC6. Feel free to make a merge
|
|
|
|
|
# request if you find out that it is booting working with newer GCCs as
|
|
|
|
|
# well. See <https://postmarketos.org/vendorkernel> for instructions.
|
|
|
|
|
if [ "${CC:0:5}" != "gcc6-" ]; then
|
|
|
|
|
CC="gcc6-$CC"
|
2018-11-30 20:56:06 +00:00
|
|
|
HOSTCC="gcc6-gcc"
|
2018-10-01 06:44:18 +00:00
|
|
|
CROSS_COMPILE="gcc6-$CROSS_COMPILE"
|
|
|
|
|
fi
|
2017-11-05 20:10:19 +00:00
|
|
|
|
|
|
|
|
# Source
|
|
|
|
|
_repository="android_kernel_samsung_d2"
|
|
|
|
|
_commit="716f00ee2e86adfd507842c5f193a738b57d3c49"
|
2020-02-28 09:59:56 +00:00
|
|
|
_config="config-$_flavor.$arch"
|
2017-11-05 20:10:19 +00:00
|
|
|
source="
|
2020-02-28 09:59:56 +00:00
|
|
|
$pkgname-$_commit.tar.gz::https://github.com/LineageOS/$_repository/archive/$_commit.tar.gz
|
2017-11-05 20:10:19 +00:00
|
|
|
$_config
|
|
|
|
|
00_fix_return_address.patch
|
|
|
|
|
00_Input-lifebook-use-static-inline-instead-of-inline-i.patch
|
|
|
|
|
00_Input-sentelic-use-static-inline-instead-of-inline.patch
|
|
|
|
|
02_gpu-msm-fix-gcc5-compile.patch
|
|
|
|
|
"
|
2020-02-28 09:59:56 +00:00
|
|
|
builddir="$srcdir/$_repository-$_commit"
|
2017-11-05 20:10:19 +00:00
|
|
|
|
|
|
|
|
prepare() {
|
|
|
|
|
default_prepare
|
2020-04-01 07:09:30 +00:00
|
|
|
. downstreamkernel_prepare
|
2017-11-05 20:10:19 +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"
|
2017-11-05 20:10:19 +00:00
|
|
|
}
|
|
|
|
|
|
|
|
|
|
sha512sums="6850231f0596dd272b4f963d20c77aee6ed16a1ba47261dbafe11ffccac695427db54efa71d070525c519885b795395e9ac6ca97fa06ccc36131aba1f95aa715 linux-samsung-i747m-716f00ee2e86adfd507842c5f193a738b57d3c49.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
|
|
|
cfe73778fe3342fa634d8b0a95d9f2fc0cee203bb2a3bbc7832947947ac84e944a920dc96ac9e851edaef577d5ced34eceed989a93b9e8c06091c5f7f47b5930 config-samsung-i747m.armhf
|
2017-11-05 20:10:19 +00:00
|
|
|
ea1d3b5a234fa565e3c1a792de48f4fc4e6023d281d303c8e319c7ef28edc5739ab0e4dea0139a41f0a5c7d03e27921ccaa214fd0ac5c72245a094ce60128864 00_fix_return_address.patch
|
|
|
|
|
5c49f6ff6773a7dc3067d2b1359648fe7a9f758b6c068d6fa69d9aaf24a291ba8022c960317d926aabc11d020a71b20c4e81a6fcf9b21ef66d9b6d065bae23e9 00_Input-lifebook-use-static-inline-instead-of-inline-i.patch
|
|
|
|
|
2d77d90b501aa8afbf81629e73fc0a2055b373942975f58277e43f398d0835b3dbbff4a1118137ec82873ba90a254fea87c1d73ba7708578f1779bd0b4c6ff2d 00_Input-sentelic-use-static-inline-instead-of-inline.patch
|
|
|
|
|
7be03a9e78b7ac330a54b1f00509caa0621a95c0c55901878ad757f9dd69cc05ba2c8b5ea987063ae1224f92c4d090d515fa5d369e7755181a4871b0d0f82881 02_gpu-msm-fix-gcc5-compile.patch"
|