2020-02-09 17:31:28 +00:00
|
|
|
# Reference: <https://postmarketos.org/vendorkernel>
|
|
|
|
|
# Kernel config based on: arch/arm/configs/tank_defconfig
|
|
|
|
|
|
2020-04-25 09:51:42 +00:00
|
|
|
pkgname=linux-amazon-tank
|
2020-02-09 17:31:28 +00:00
|
|
|
pkgver=3.10.54
|
*/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-02-09 17:31:28 +00:00
|
|
|
pkgdesc="Amazon Fire TV Stick (2nd Gen) kernel fork"
|
|
|
|
|
arch="armv7"
|
|
|
|
|
_carch="arm"
|
|
|
|
|
_flavor="amazon-tank"
|
|
|
|
|
url="https://kernel.org"
|
|
|
|
|
license="GPL-2.0-only"
|
2020-04-21 01:24:27 +00:00
|
|
|
options="!strip !check !tracedeps pmb:cross-native"
|
2020-02-09 17:31:28 +00:00
|
|
|
makedepends="perl sed installkernel bash gmp-dev bc linux-headers elfutils-dev devicepkg-dev gcc4 xz"
|
|
|
|
|
|
|
|
|
|
# Compiler: GCC 4 (doesn't compile with newer versions)
|
|
|
|
|
if [ "${CC:0:5}" != "gcc4-" ]; then
|
|
|
|
|
CC="gcc4-$CC"
|
|
|
|
|
HOSTCC="gcc4-gcc"
|
|
|
|
|
CROSS_COMPILE="gcc4-$CROSS_COMPILE"
|
|
|
|
|
fi
|
|
|
|
|
|
|
|
|
|
# Source
|
|
|
|
|
_repository="android_kernel_amazon_mt8127"
|
|
|
|
|
_commit="2861aa5f5e0bbb526072d75f24ef3af875519234"
|
|
|
|
|
_config="config-$_flavor.$arch"
|
|
|
|
|
source="
|
|
|
|
|
$pkgname-$_commit.tar.gz::https://github.com/cmtank/$_repository/archive/$_commit.tar.gz
|
|
|
|
|
$_config
|
|
|
|
|
01_ozmo_fix_trace.patch
|
|
|
|
|
02_thermal_fix_include.patch
|
|
|
|
|
"
|
|
|
|
|
builddir="$srcdir/$_repository-$_commit"
|
|
|
|
|
|
|
|
|
|
prepare() {
|
|
|
|
|
default_prepare
|
2020-04-01 07:09:30 +00:00
|
|
|
. downstreamkernel_prepare
|
2020-02-09 17:31:28 +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"
|
2020-02-09 17:31:28 +00:00
|
|
|
}
|
|
|
|
|
|
|
|
|
|
sha512sums="bef51789afd0174f0c88d7cd1f038a754e85a8fa2a159036f154d08b8812e7fcee762d9e231cf1397b66afb846f453e00aae98f74c4c143d83b57b7c83616fe9 linux-amazon-tank-2861aa5f5e0bbb526072d75f24ef3af875519234.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
|
|
|
a782397ba9922b5d7ce5de3ae08b028a0f9ed2ef4751a9abfbdbbad62cff49e1e834ed299607bc984388a35f9128524efb1ea95c94cbb3277925eb897e88bc07 config-amazon-tank.armv7
|
2020-02-09 17:31:28 +00:00
|
|
|
0aa0b433e0b74751351c6782b168b91ffb1cf4c4d305ff1e3e39f3cc4f6321d5e3488a531a1fcac0bb92a2997002d5c1608a55573a7bbf43e32cb612b04793b8 01_ozmo_fix_trace.patch
|
|
|
|
|
158eeb7905fd341432f21a9a16921468285c14dd4a044228119a232e1ce9c77e30c513f62737ebdb40fb27cf4d30542cdb4e62bf2982f8827e195c10d7d40d16 02_thermal_fix_include.patch"
|