2018-04-21 14:55:39 +00:00
|
|
|
# Kernel config based on: arch/arm/configs/golden_android_defconfig
|
|
|
|
|
2020-04-25 09:51:42 +00:00
|
|
|
pkgname=linux-samsung-golden
|
2018-04-21 14:55:39 +00:00
|
|
|
pkgver=3.0.31
|
*/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=2
|
2018-04-21 14:55:39 +00:00
|
|
|
pkgdesc="Samsung Galaxy SIII mini kernel fork"
|
2019-11-03 18:54:55 +00:00
|
|
|
arch="armv7"
|
2018-04-21 14:55:39 +00:00
|
|
|
_carch="arm"
|
2019-11-03 19:06:05 +00:00
|
|
|
_flavor="samsung-golden"
|
2018-04-21 14:55:39 +00:00
|
|
|
url="https://kernel.org"
|
2019-11-03 19:06:05 +00:00
|
|
|
license="GPL-2.0-or-later"
|
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-04-21 14:55:39 +00:00
|
|
|
|
|
|
|
# Source
|
|
|
|
_repository="android_kernel_samsung_golden"
|
|
|
|
_commit="2662dc4f65ef3ad5eeb4222d3aad5dd418a04510"
|
2020-02-28 09:59:56 +00:00
|
|
|
_config="config-$_flavor.$arch"
|
2018-04-21 14:55:39 +00:00
|
|
|
source="
|
2020-02-28 09:59:56 +00:00
|
|
|
$pkgname-$_commit.tar.gz::https://github.com/NovaFusion/$_repository/archive/$_commit.tar.gz
|
2018-04-21 14:55:39 +00:00
|
|
|
$_config
|
2020-11-09 10:06:09 +00:00
|
|
|
timeconst.pl-Eliminate-Perl-warning.patch
|
2018-04-21 14:55:39 +00:00
|
|
|
00_fix_makefile.patch
|
|
|
|
01_fix_return_address.patch
|
|
|
|
03_fix_rndis.patch
|
2018-05-05 19:44:34 +00:00
|
|
|
04_fix_bcma.patch
|
|
|
|
05_change_dhd_firmware_path.patch
|
2018-04-21 14:55:39 +00:00
|
|
|
"
|
2020-02-28 09:59:56 +00:00
|
|
|
builddir="$srcdir/$_repository-$_commit"
|
2018-04-21 14:55:39 +00:00
|
|
|
|
|
|
|
prepare() {
|
|
|
|
default_prepare
|
2020-04-01 07:09:30 +00:00
|
|
|
. downstreamkernel_prepare
|
2018-04-21 14:55:39 +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-12-12 17:38:19 +00:00
|
|
|
|
2018-05-05 19:44:34 +00:00
|
|
|
# Modules
|
|
|
|
unset LDFLAGS
|
|
|
|
make ARCH="$_carch" CC="${CC:-gcc}" \
|
|
|
|
KBUILD_BUILD_VERSION="$((pkgrel + 1))-postmarketOS" \
|
|
|
|
INSTALL_MOD_PATH="$pkgdir" INSTALL_MOD_STRIP=1 \
|
|
|
|
modules_install
|
2018-04-21 14:55:39 +00:00
|
|
|
}
|
|
|
|
|
2019-11-03 19:06:05 +00:00
|
|
|
sha512sums="318586c486d831719d678e7645c073146b6d2cfc60ac0b8b54ddc6e545723d207d46a7acd78d944e7a855e3a5181fa8ccf863d9dd0c10129a6814e9e7e70a2fa linux-samsung-golden-2662dc4f65ef3ad5eeb4222d3aad5dd418a04510.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
|
|
|
d850d07ccef7a0397a0ec28761115b8522feb0b46097bb5ff7706f74492a10126be5d58c14dcaef8295ef221cbdab9be39c5db43a35acb157d4737ddd495d23f config-samsung-golden.armv7
|
2020-11-09 10:06:09 +00:00
|
|
|
1fcfb5f06a2bfdcc55d53054ca80d1b989599a39a5379d057a0724fc405187d74da4309a650e70b9c79d39444e81923cfc5c9199ed8c0a77c83dcd7998446bb7 timeconst.pl-Eliminate-Perl-warning.patch
|
2018-04-21 14:55:39 +00:00
|
|
|
1b3ffbfd511af7a81590e0004bcf45b89592d6bf38cc3dd48af1e227f879426894eede34376ac708e56e84217af6ff22ee16526b3e64905ef30f0d101bbcbc29 00_fix_makefile.patch
|
|
|
|
ea1d3b5a234fa565e3c1a792de48f4fc4e6023d281d303c8e319c7ef28edc5739ab0e4dea0139a41f0a5c7d03e27921ccaa214fd0ac5c72245a094ce60128864 01_fix_return_address.patch
|
2018-05-05 19:44:34 +00:00
|
|
|
6585c67450f1ef6d0c165ce4cb5c64f64d779147d1390558bf72cd40da5a33d53de6fd3c67e5ab864c14b3f67602bbe3060eea07c85b19bb82a0735024b369eb 03_fix_rndis.patch
|
|
|
|
31fe10c659d59fd086b49c20412a27cc6241e650cda1200efe86cedfc5d9ac380a3c7ff931161a40b26ab49b6e3fa04d27316efd66fba6605a5e35ef526b41e4 04_fix_bcma.patch
|
2019-12-12 17:38:19 +00:00
|
|
|
3665c85be5fb7931f6e83fa98a6c4ab876f97949cfbbe04bdcfe1175ed5ef6fdb3c12558d678d30f6c60f5fa5e79cf7aa8fe1910e4bd36ee1ba0f20cef9163ea 05_change_dhd_firmware_path.patch"
|