forge/pmaports
1
0
Fork 0
Code Issues 2 Pull requests Projects Releases Packages Wiki Activity Actions
pmaports/device/archived/linux-oneplus-msm8998-downstream/APKBUILD

66 lines
3.3 KiB
Text
Raw Normal View History

device: rename unmaintained to archived (MR 5046) Unmaintained is a name which on multiple occasions have seen lead to confusion with people having the impression that unmaintained is for all unmaintained devices, which is not how we're really using it. Many devices in testing do not actually have a maintainer, yet there has been no push to move these out of there and into unmaintained. I think this is a result of that unmaintained was introduced not to keep unmaintained ports but rather a place to store ports that have a better replacement but where the inferior one still holds some sort of value, such as for debugging purposes. These ports also are not necessarily entirely unmaintained and see more fixes than many ports in testing. While one approach to solving this problem could be to simply moving all unmaintained ports to unmaintained, I think this comes with some problems: It would require an initial effort to figure out which ports are indeed unmaintained and which just don't have a maintained noted in the package, and given how many ports there are in testing this would be a big endeavour. It would also require continuous work on moving ports into unmaintained as the maintainers go silent if we are to keep testing and unmaintained's state consistent with reality. Additionally, just because a port doesn't have a maintainer on paper doens't mean that there aren't people who aren't willing to fix it up if there are issues that arise. As such, I think the way to go is renaming unmaintained to better reflect the original intent. Thanks to Luca Weiss for suggesting "archive", and to Arnav Singh for suggesting that "archived" would match the other category names better.
2024-04-18 17:19:42 +00:00
# Archived: EoL downstream kernel, only for reference. Use mainline kernel (linux-postmarketos-qcom-msm8998)!
oneplus-cheeseburger: new device (OnePlus 5) (!908)
2020-01-28 10:42:25 +00:00
# Reference: <https://postmarketos.org/vendorkernel>
# Kernel config based on: arch/arm64/configs/lineage_oneplus5_defconfig (https://git.io/JvmDf)
linux-oneplus-msm8998: move to unmaintained (MR 3336) The downstream kernel has barely any functionality without libhybris (which is not coming back to pmOS) so move everything related to the OnePlus 5/5T downstream ports to downstream since a working mainline port is much more feature rich.
2022-08-02 20:16:58 +00:00
pkgname=linux-oneplus-msm8998-downstream
linux-oneplus-cheeseburger: update to v4.4.217 (!1110) Might as well update the downstream kernel when someone (nathanchance) is merging in updates as they come out for the linux-stable 4.4.y series ¯\_(ツ)_/¯
2020-03-27 13:21:21 +00:00
pkgver=4.4.217
linux-oneplus-msm8998: move to unmaintained (MR 3336) The downstream kernel has barely any functionality without libhybris (which is not coming back to pmOS) so move everything related to the OnePlus 5/5T downstream ports to downstream since a working mainline port is much more feature rich.
2022-08-02 20:16:58 +00:00
pkgrel=0
oneplus-cheeseburger: rename kernel package to linux-oneplus-msm8998 (!1110) This is in preparation for adding in support for the OnePlus 5T (dumpling) on top of the regular OnePlus 5 (cheeseburger). Both devices use the same kernel so the name change just makes sense.
2020-03-27 15:14:05 +00:00
pkgdesc="OnePlus 5/5T downstream kernel fork"
oneplus-cheeseburger: new device (OnePlus 5) (!908)
2020-01-28 10:42:25 +00:00
arch="aarch64"
_carch="arm64"
linux-oneplus-msm8998: move to unmaintained (MR 3336) The downstream kernel has barely any functionality without libhybris (which is not coming back to pmOS) so move everything related to the OnePlus 5/5T downstream ports to downstream since a working mainline port is much more feature rich.
2022-08-02 20:16:58 +00:00
_flavor="oneplus-msm8998-downstream"
oneplus-cheeseburger: new device (OnePlus 5) (!908)
2020-01-28 10:42:25 +00:00
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"
oneplus-cheeseburger: new device (OnePlus 5) (!908)
2020-01-28 10:42:25 +00:00
makedepends="perl sed installkernel bash gmp-dev bc linux-headers elfutils-dev devicepkg-dev gcc6 openssl-dev"
# Compiler: GCC 6 (latest doesn't boot to initramfs)
if [ "${CC:0:5}" != "gcc6-" ]; then
CC="gcc6-$CC"
HOSTCC="gcc6-gcc"
CROSS_COMPILE="gcc6-$CROSS_COMPILE"
fi
# Source
_repository="op5"
linux-oneplus-cheeseburger: update to v4.4.217 (!1110) Might as well update the downstream kernel when someone (nathanchance) is merging in updates as they come out for the linux-stable 4.4.y series ¯\_(ツ)_/¯
2020-03-27 13:21:21 +00:00
_commit="dac686aa9a9491551e70a6d35d8636f823eb97e9"
oneplus-cheeseburger: new device (OnePlus 5) (!908)
2020-01-28 10:42:25 +00:00
_config="config-$_flavor.$arch"
source="
$pkgname-$_commit.tar.gz::https://github.com/android-linux-stable/$_repository/archive/$_commit.tar.gz
$_config
0001-use-relative-header-includes.patch
0002-fix-TRACE_INCLUDE_PATH-paths.patch
0003-fix-synaptics_s3320-touchscreen-driver-input.patch
0004-disable-interfering-bt_power-rfkill.patch
0005-update-msm8998-qpnp-rtc-driver-src-with-sm8150.patch
0006-disable-various-spammy-driver-logging.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
linux4.2-gcc10-extern_YYLOC_global_declaration.patch
oneplus-cheeseburger: new device (OnePlus 5) (!908)
2020-01-28 10:42:25 +00:00
"
builddir="$srcdir/$_repository-$_commit"
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
oneplus-cheeseburger: new device (OnePlus 5) (!908)
2020-01-28 10:42:25 +00:00
}
build() {
unset LDFLAGS
make ARCH="$_carch" CC="${CC:-gcc}" \
KBUILD_BUILD_VERSION="$((pkgrel + 1 ))-postmarketOS"
}
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"
oneplus-cheeseburger: new device (OnePlus 5) (!908)
2020-01-28 10:42:25 +00:00
}
linux-oneplus-msm8998: move to unmaintained (MR 3336) The downstream kernel has barely any functionality without libhybris (which is not coming back to pmOS) so move everything related to the OnePlus 5/5T downstream ports to downstream since a working mainline port is much more feature rich.
2022-08-02 20:16:58 +00:00
sha512sums="
fea5a566ce4f1ef93e08cdd4d0edb3afe358105865b8583231cdeaccaaa3484d567230fdd4b3cea5e77fa1b7ff9bf9486b8d1ba1c757fc3477db35d9a93f3db4 linux-oneplus-msm8998-downstream-dac686aa9a9491551e70a6d35d8636f823eb97e9.tar.gz
2fa4fe807711b7595c92488f3f16c287b40663dd16cea22e406e57a6c888a9151987490fb910c48ca766af398ed6612336df7c7662234a839429d15de1256599 config-oneplus-msm8998-downstream.aarch64
oneplus-cheeseburger: new device (OnePlus 5) (!908)
2020-01-28 10:42:25 +00:00
f369bb6510a5c0581eb2db6ef565d0e93e117b5960c91f52bebd5aa931d65fe91bdc0ec9673107756aa1b5118208d75af116925630aed9025a8f5e303ae1f980 0001-use-relative-header-includes.patch
a484dc777b37b43eb54f8beb20eef51b7a9177928f97f1b200951c6ece70805e7fa3762f4ad0686525021254fd1f0b5d36c207cf27a04ec65cfe55f88c3d1c12 0002-fix-TRACE_INCLUDE_PATH-paths.patch
a29c158497e8ef4afddce57e42e54de81629ddf85df4a229282b528ec63475bfa5ed4cc6ff5f77d22300c7124655807355aa7b0cc25d8b02e122b752777f677a 0003-fix-synaptics_s3320-touchscreen-driver-input.patch
1afb3a4e6af51d073a6e9d3352b0b5ab2918018d2ada972e72209eba3fc5b98926e691ff0d641a9d03a4ce8030e6ed15dff54b3720c751ab7134db53bfd2e685 0004-disable-interfering-bt_power-rfkill.patch
44031dfaa8fe9a073924fd3549ebb158d32ec2925f29f0a0ca6b1959fb4597dd32232035253bd896985a7d81235c1fbdd917347d7ff5257103be8ee4bb02e5fe 0005-update-msm8998-qpnp-rtc-driver-src-with-sm8150.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
083da52f3a2bfa745104690773539426afff3150e81ea25a377d51f7253d83f6eedfb62644907171e142db114435cc6a3e0627b9dc04a99ae6e5796dc8159209 0006-disable-various-spammy-driver-logging.patch
linux-oneplus-msm8998: move to unmaintained (MR 3336) The downstream kernel has barely any functionality without libhybris (which is not coming back to pmOS) so move everything related to the OnePlus 5/5T downstream ports to downstream since a working mainline port is much more feature rich.
2022-08-02 20:16:58 +00:00
eaf2e61fcb508cdd239b8fed209d2a09ecac77287f6b46d003918fdf1c6fa2ee63f7390f3ff7c49029b8ed6cbcdd81c7e9a4b1ece9f5060b6fc84e322bd47f41 linux4.2-gcc10-extern_YYLOC_global_declaration.patch
"
Reference in a new issue Copy permalink