2020-05-31 12:21:35 +00:00
|
|
|
# Reference: <https://postmarketos.org/vendorkernel>
|
|
|
|
|
# Kernel config based on: arch/arm/configs/lineage_s3ve3gxx_defconf
|
|
|
|
|
|
|
|
|
|
pkgname=linux-samsung-s3ve3g
|
|
|
|
|
pkgver=3.4.113
|
*/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-05-31 12:21:35 +00:00
|
|
|
pkgdesc="Samsung Galaxy S III Neo kernel fork"
|
|
|
|
|
arch="armv7"
|
|
|
|
|
_carch="arm"
|
|
|
|
|
_flavor="samsung-s3ve3g"
|
|
|
|
|
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 dtbtool xz"
|
|
|
|
|
|
|
|
|
|
# Source
|
|
|
|
|
_repository="android_kernel_samsung_msm8226"
|
|
|
|
|
_commit="011bada1b7d038d703f4819176cfdf59b3e34e20"
|
|
|
|
|
_config="config-$_flavor.$arch"
|
|
|
|
|
source="
|
|
|
|
|
$pkgname-$_commit.tar.gz::https://github.com/LineageOS/$_repository/archive/$_commit.tar.gz
|
|
|
|
|
$_config
|
|
|
|
|
gcc7-give-up-on-ilog2-const-optimizations.patch
|
|
|
|
|
gcc8-fix-put-user.patch
|
|
|
|
|
kernel-use-the-gnu89-standard-explicitly.patch
|
|
|
|
|
0001-remove-Unified-Sysfs-for-GPU-kernel-option.patch
|
|
|
|
|
0002-always-reserve-framebuffer-memory.patch
|
|
|
|
|
0003-fix-video-argb-setting.patch
|
|
|
|
|
0004-usb_gadget-set-random-rndis-host-MAC-address-to-prev.patch
|
|
|
|
|
0005-alternative-patch-to-fix-refresh-rate.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"
|
|
|
|
|
|
|
|
|
|
# Master DTB (deviceinfo_bootimg_qcdt)
|
|
|
|
|
dtbTool -p scripts/dtc/ -o "$_outdir/arch/$_carch/boot"/dt.img "$_outdir/arch/$_carch/boot/"
|
|
|
|
|
install -Dm644 "$_outdir/arch/$_carch/boot"/dt.img "$pkgdir"/boot/dt.img
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
sha512sums="c2984fc0707e00a718c486f31491921c5112ec0c13d4d9d5032f77765859fa4f1989bdcedd8763bb26b6fbbaeae8cef388b1f71ee36e558b1f13950fa5b56071 linux-samsung-s3ve3g-011bada1b7d038d703f4819176cfdf59b3e34e20.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
|
|
|
79c7aa697eb3e2856baed7db6c55b811f14120ac19392653856a88c125573a80bfbc093b865b3c6a81a5c6c30bbc58291476f45c42b4ca21b94b9ce304b497f9 config-samsung-s3ve3g.armv7
|
2020-05-31 12:21:35 +00:00
|
|
|
77eba606a71eafb36c32e9c5fe5e77f5e4746caac292440d9fb720763d766074a964db1c12bc76fe583c5d1a5c864219c59941f5e53adad182dbc70bf2bc14a7 gcc7-give-up-on-ilog2-const-optimizations.patch
|
|
|
|
|
197d40a214ada87fcb2dfc0ae4911704b9a93354b75179cd6b4aadbb627a37ec262cf516921c84a8b1806809b70a7b440cdc8310a4a55fca5d2c0baa988e3967 gcc8-fix-put-user.patch
|
|
|
|
|
ad0182a483791fc88e058838bc331b2f04a75ba291e763767babdb815efadfc3b4fda97e69e2e3f00a426cabea088e35297a92bd287592597d1e309be68ee92c kernel-use-the-gnu89-standard-explicitly.patch
|
|
|
|
|
472f2aacb61f66a253113bce3846cb132ce73cf98df4b08245184ac96857f8d3657e80c5ecdabfc04f61ea0971a0e4d2c64dc5886f6c949b560e018e855a5a95 0001-remove-Unified-Sysfs-for-GPU-kernel-option.patch
|
|
|
|
|
99710981a40c5ce465fc6de9c438349224c52a4175a0bcbec95bd4d860a44abfa0d59151e94b85a40f049aadff66cb02b74ea84c51424ec5b19b76b17edb5b20 0002-always-reserve-framebuffer-memory.patch
|
|
|
|
|
ff4ebae2d4e9d3c78849d9f00879d91a4d554ae68eebe9853388154686f9bd48de1c68e586c855204e6bff61972d2fbc77c5b1c9c6f9ff66e101bc2d04cb5e29 0003-fix-video-argb-setting.patch
|
|
|
|
|
9b7fc59035714badcecb5138da4b58d2bda5b8260a04cbad9e1baa57ec6cdebfeea1752744e551a2341e164da78c119564892b43c823aded2f50f2417bbc47ce 0004-usb_gadget-set-random-rndis-host-MAC-address-to-prev.patch
|
|
|
|
|
2f8305cd137e5fbc888d3c81201976ae2819275715dde8ee6f63845a0d36021566af8e78ab765e084b6def1bb10cfc4dde1714a472ea4fab8a9c95e7bee9e2c5 0005-alternative-patch-to-fix-refresh-rate.patch"
|