2018-05-12 18:12:40 +00:00
|
|
|
# Kernel config based on: arch/arm/configs/pxa986_lt023g_blackhawk_defconfig
|
|
|
|
|
2020-04-25 09:51:42 +00:00
|
|
|
pkgname=linux-samsung-lt023g
|
2018-05-12 18:12:40 +00:00
|
|
|
pkgver=3.4.5
|
*/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=6
|
2018-05-12 18:12:40 +00:00
|
|
|
pkgdesc="Samsung Galaxy Tab 3 7.0 kernel fork"
|
2019-06-28 19:02:02 +00:00
|
|
|
arch="armv7"
|
2018-05-12 18:12:40 +00:00
|
|
|
_carch="arm"
|
|
|
|
_flavor="samsung-lt023g"
|
|
|
|
url="https://github.com/kumajaya/android_kernel_samsung_lt02"
|
|
|
|
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 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
|
2018-05-12 18:12:40 +00:00
|
|
|
|
|
|
|
# Source
|
|
|
|
_repository="android_kernel_samsung_lt02"
|
|
|
|
_commit="c6fb6f677aa195b07348eb7777322ca956f9c44c"
|
2020-02-28 09:59:56 +00:00
|
|
|
_config="config-$_flavor.$arch"
|
2018-05-12 18:12:40 +00:00
|
|
|
source="
|
2020-02-28 09:59:56 +00:00
|
|
|
$pkgname-$_commit.tar.gz::https://github.com/kumajaya/$_repository/archive/$_commit.tar.gz
|
2018-05-12 18:12:40 +00:00
|
|
|
$_config
|
2020-11-09 10:06:09 +00:00
|
|
|
timeconst.pl-Eliminate-Perl-warning.patch
|
2018-05-12 18:12:40 +00:00
|
|
|
455bd4c430b0c0a361f38e8658a0d6cb469942b5.patch
|
|
|
|
418df63adac56841ef6b0f1fcf435bc64d4ed177.patch
|
|
|
|
"
|
2020-02-28 09:59:56 +00:00
|
|
|
builddir="$srcdir/$_repository-$_commit"
|
2018-05-12 18:12:40 +00:00
|
|
|
|
|
|
|
prepare() {
|
|
|
|
default_prepare
|
2020-04-01 07:09:30 +00:00
|
|
|
. downstreamkernel_prepare
|
2018-05-12 18:12:40 +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"
|
2018-05-12 18:12:40 +00:00
|
|
|
}
|
|
|
|
|
|
|
|
sha512sums="41b0dc94d29e1ad75bcb309aebefc58302b5176be30cafd827b7f69b44805b84d44de93dfc363e671a421623ad2b6d264edbc74976106ba52f0c249d268622f1 linux-samsung-lt023g-c6fb6f677aa195b07348eb7777322ca956f9c44c.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
|
|
|
2138534d9602e2f53e449385385ba7a9e4918c47c76b12d13f81151110c58957be9ad8e0ba0456e2a630574d1f04297863f041db551baad3c7ff592a923e8166 config-samsung-lt023g.armv7
|
2020-11-09 10:06:09 +00:00
|
|
|
1fcfb5f06a2bfdcc55d53054ca80d1b989599a39a5379d057a0724fc405187d74da4309a650e70b9c79d39444e81923cfc5c9199ed8c0a77c83dcd7998446bb7 timeconst.pl-Eliminate-Perl-warning.patch
|
2018-05-12 18:12:40 +00:00
|
|
|
efd1641c0892fddb9c5feea3e49e534fed311b01f0576688b5af766e0160850822d0eb8e296b08c5f82b586d5d0336a98e8e86707ba9af7fcf36fc89f0b288eb 455bd4c430b0c0a361f38e8658a0d6cb469942b5.patch
|
|
|
|
5c080c27716d124616e4e684fc63bffb2665f00de06e894dfd78f58588feec2fec858fe8234b054061e3db14d28cb90fbac53f4b54c4fac5946d843cf038386c 418df63adac56841ef6b0f1fcf435bc64d4ed177.patch"
|