forge/pmaports
1
0
Fork 0
Code Issues 2 Pull requests Projects Releases Packages Wiki Activity Actions
pmaports/device/testing/linux-samsung-matissewifi/APKBUILD

70 lines
3.5 KiB
Text
Raw Normal View History

samsung-matissewifi: new device (!560)
2019-08-18 10:36:52 +00:00
# Reference: <https://postmarketos.org/vendorkernel>
# Kernel config based on: arch/arm/configs/cyanogenmod_matissewifi_defconfig
*: remove quotes around pkgname (MR 1186) TP:[AL3]:APKBUILD:5:pkgname must not be quoted [skip ci]: won't finish within 3 hours
2020-04-25 09:51:42 +00:00
pkgname=linux-samsung-matissewifi
samsung-matissewifi: new device (!560)
2019-08-18 10:36:52 +00:00
pkgver=3.4.0
*/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
samsung-matissewifi: new device (!560)
2019-08-18 10:36:52 +00:00
pkgdesc="Samsung Galaxy Tab 4 10.1 kernel fork"
arch="armv7"
_carch="arm"
_flavor="samsung-matissewifi"
url="https://kernel.org"
license="GPL-2.0-only"
cross/arch-bin-masquerade, main/anbox-image, linux-*: use pmb:cross-native (MR 1169) https://gitlab.com/postmarketOS/pmbootstrap/-/issues/1910 [skip ci]: CI fails because it can't download every release tarball to check checksums in 3h.
2020-04-21 01:24:27 +00:00
options="!strip !check !tracedeps pmb:cross-native"
samsung-matissewifi: new device (!560)
2019-08-18 10:36:52 +00:00
makedepends="perl sed installkernel bash gmp-dev bc linux-headers elfutils-dev dtbtool devicepkg-dev"
# Source
_repository="android_kernel_samsung_matissewifi"
_commit="0761bc76449b73747698b76a155883342192106f"
device/linux-*: remove unneeded braces from variables (!1007) sed -i -E 's/\$\{(\w+)\}/$\1/g' linux-*/APKBUILD Manually revert ${CROSS_COMPILE} in linux-motorola-maserati.
2020-02-28 09:59:56 +00:00
_config="config-$_flavor.$arch"
samsung-matissewifi: new device (!560)
2019-08-18 10:36:52 +00:00
source="
device/linux-*: remove unneeded braces from variables (!1007) sed -i -E 's/\$\{(\w+)\}/$\1/g' linux-*/APKBUILD Manually revert ${CROSS_COMPILE} in linux-motorola-maserati.
2020-02-28 09:59:56 +00:00
$pkgname-$_commit.tar.gz::https://github.com/GalaxyTab4/$_repository/archive/$_commit.tar.gz
samsung-matissewifi: new device (!560)
2019-08-18 10:36:52 +00:00
$_config
gcc7-give-up-on-ilog2-const-optimizations.patch
gcc8-fix-put-user.patch
device/testing/linux-*: get building again (MR 1684) Mostly the GCC10 yylloc failure was seen but several others have been observed: * wireguard script was silently failing * several gcc10 x86 errors * a checksum from kernel.org has changed Now we have 3 different gcc10 yylloc patches: gcc10-extern_YYLOC_global_declaration.patch: Linux < 4.2 linux4.2-gcc10-extern_YYLOC_global_declaration.patch: Linux 4.2+ linux4.17-gcc10-extern_YYLOC_global_declaration.patch: Linux 4.17+ [ci:skip-build] [ci:ignore-count] [ci:skip-vercheck]
2020-11-04 12:48:12 +00:00
gcc10-extern_YYLOC_global_declaration.patch
samsung-matissewifi: new device (!560)
2019-08-18 10:36:52 +00:00
kernel-use-the-gnu89-standard-explicitly.patch
00_smd_private.patch
01_timeconst.patch
02_mdss_mdp_trace.patch
03_qdsp6v2.patch
04_q6voice.patch
random_mac.patch
"
device/linux-*: remove unneeded braces from variables (!1007) sed -i -E 's/\$\{(\w+)\}/$\1/g' linux-*/APKBUILD Manually revert ${CROSS_COMPILE} in linux-motorola-maserati.
2020-02-28 09:59:56 +00:00
builddir="$srcdir/$_repository-$_commit"
samsung-matissewifi: new device (!560)
2019-08-18 10:36:52 +00:00
prepare() {
default_prepare
**/linux-*: update usage of downstreamkernel_prepare helper (!1084) [skip-ci]: just downloading all kernel sources takes about one hour and ollieparanoid wants to merge it now. This already ran successfully with [ci:skip-build] and [ci:skip-vercheck].
2020-04-01 07:09:30 +00:00
. downstreamkernel_prepare
samsung-matissewifi: new device (!560)
2019-08-18 10:36:52 +00:00
}
build() {
unset LDFLAGS
make ARCH="$_carch" CC="${CC:-gcc}" \
KBUILD_BUILD_VERSION="$((pkgrel + 1 ))-postmarketOS"
# Generate master DTB (deviceinfo_bootimg_qcdt)
dtbTool -s 2048 -p "scripts/dtc/" -o "arch/arm/boot/dt.img" "arch/arm/boot/"
}
package() {
device/linux-*: use downstreamkernel_* helpers (!976) [ci:skip-build] [ci:skip-vercheck]
2020-02-18 08:34:06 +00:00
downstreamkernel_package "$builddir" "$pkgdir" "$_carch" "$_flavor"
samsung-matissewifi: new device (!560)
2019-08-18 10:36:52 +00:00
# Master DTB (deviceinfo_bootimg_qcdt)
install -Dm644 "$builddir/arch/arm/boot/dt.img" \
"$pkgdir/boot/dt.img"
}
sha512sums="fe9bfcd7b16519b60d555492db9ca1f9afe5574da93931221b8aae3b06ac768ead456414e08a9aa08cde57ae5d07a59c9052d6decd15e1cc56ce379c4c712ec4 linux-samsung-matissewifi-0761bc76449b73747698b76a155883342192106f.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
dd0c902461d33dc6fb4e58aeaac2ea53b612af9afa639de67cb0eafe38c0a2ea3b35357c5021717c0e7bf7cb0c7e33272b17f5fcb320246f0e11916f895fca93 config-samsung-matissewifi.armv7
samsung-matissewifi: new device (!560)
2019-08-18 10:36:52 +00:00
77eba606a71eafb36c32e9c5fe5e77f5e4746caac292440d9fb720763d766074a964db1c12bc76fe583c5d1a5c864219c59941f5e53adad182dbc70bf2bc14a7 gcc7-give-up-on-ilog2-const-optimizations.patch
197d40a214ada87fcb2dfc0ae4911704b9a93354b75179cd6b4aadbb627a37ec262cf516921c84a8b1806809b70a7b440cdc8310a4a55fca5d2c0baa988e3967 gcc8-fix-put-user.patch
device/testing/linux-*: get building again (MR 1684) Mostly the GCC10 yylloc failure was seen but several others have been observed: * wireguard script was silently failing * several gcc10 x86 errors * a checksum from kernel.org has changed Now we have 3 different gcc10 yylloc patches: gcc10-extern_YYLOC_global_declaration.patch: Linux < 4.2 linux4.2-gcc10-extern_YYLOC_global_declaration.patch: Linux 4.2+ linux4.17-gcc10-extern_YYLOC_global_declaration.patch: Linux 4.17+ [ci:skip-build] [ci:ignore-count] [ci:skip-vercheck]
2020-11-04 12:48:12 +00:00
2b48f1bf0e3f70703d2cdafc47d5e615cc7c56c70bec56b2e3297d3fa4a7a1321d649a8679614553dde8fe52ff1051dae38d5990e3744c9ca986d92187dcdbeb gcc10-extern_YYLOC_global_declaration.patch
samsung-matissewifi: new device (!560)
2019-08-18 10:36:52 +00:00
ad0182a483791fc88e058838bc331b2f04a75ba291e763767babdb815efadfc3b4fda97e69e2e3f00a426cabea088e35297a92bd287592597d1e309be68ee92c kernel-use-the-gnu89-standard-explicitly.patch
39892cc41e484c51dccc29cadea475aaf99772bafb19231086b614b9eaee520843cd9361c89a6780229961e0ebf4bbf0e115d0e30f8302944b78091fcf7900e7 00_smd_private.patch
a2bb98fb8d988bbb659cae00fbaca360828300e9b98b90aed5ee0dd839c3f740696df4094a9021b813cbada06820d115aabed581a47cdd2c947e8d853c20b145 01_timeconst.patch
8dd3c227af5c379eedecdabe64a481de3e8241431b5d3d3984ffad65ee74706860115eb1b797afe05f6c360f6696bcb7165fa7d634a4a7a147d98f45cbb5246d 02_mdss_mdp_trace.patch
1465b7f08dd4d7956c6651da3767648db085f4af8014fd3b24547626ba608734a0c6d8e86ffe086d81817c29f0d8e284e21a3ba50f51cd94ab42935bc124ad30 03_qdsp6v2.patch
4e7484eaa142e013c9aee12053d91a65983f7629d2b923566d4431143fa0529988dbc28b01dee21336995090ce8127b2ba79208bf61df359632bfeebae9c6618 04_q6voice.patch
27f890cf82027649ba742b606a87ce6a82f9685b075bb7b50bffec77221e70434ee78d118d39048350537c5ecdad208658967e492eeeb997e7f6884fa78ac696 random_mac.patch"
Reference in a new issue Copy permalink