forge/pmaports
1
0
Fork 0
Code Issues 2 Pull requests Projects Releases Packages Wiki Activity Actions
pmaports/device/community/device-motorola-harpia/APKBUILD

42 lines
1.2 KiB
Text
Raw Normal View History

Initial support for Motorola Moto G4 Play (motorola-harpia) (#1437) Currently, Weston boots with a working touch interface, and USB networking.
2018-04-22 21:12:48 +00:00
# Reference: <https://postmarketos.org/devicepkg>
treewide: remove inactive maintainers (MR 3820) Remove maintainers who could not be reached to test v22.12. Add exkc as maintainer for firmware-pine64-rockpro64 as discussed in review of this patch. [ci:skip-build]: already built successfully in CI
2023-01-22 21:02:00 +00:00
# Maintainer: Minecrell <minecrell@minecrell.net>
*: 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=device-motorola-harpia
Initial support for Motorola Moto G4 Play (motorola-harpia) (#1437) Currently, Weston boots with a working touch interface, and USB networking.
2018-04-22 21:12:48 +00:00
pkgdesc="Motorola Moto G4 Play"
community/<msm8916>: use _pmb_select="..." instead of kernel variants (MR 2632)
2021-10-24 12:48:45 +00:00
pkgver=7
treewide: remove inactive maintainers (MR 3820) Remove maintainers who could not be reached to test v22.12. Add exkc as maintainer for firmware-pine64-rockpro64 as discussed in review of this patch. [ci:skip-build]: already built successfully in CI
2023-01-22 21:02:00 +00:00
pkgrel=2
Initial support for Motorola Moto G4 Play (motorola-harpia) (#1437) Currently, Weston boots with a working touch interface, and USB networking.
2018-04-22 21:12:48 +00:00
url="https://postmarketos.org"
license="MIT"
motorola-harpia: upgrade to mainline kernel (!682) Support for the downstream kernel has been removed entirely. This is because the downstream kernel only has support for the armhf architecture, whereas linux-postmarketos-qcom-msm8916 is only built for aarch64. Since pmbootstrap has no way to handle having two kernels on differing architectures, the decision was made to remove the downstream kernel and only support mainline.
2019-10-13 11:00:28 +00:00
arch="aarch64"
device-*: don't use noarch anymore Use the device's architecture instead of noarch. Because the device packages should never be built for other architectures, even if all depends can be built for other arches as well. This simplifies package building as part of the new build infrastructure effort. pmbootstrap has also been changed to output this by default in aportgen.
2018-11-07 06:45:58 +00:00
options="!check !archcheck"
community/<msm8916>: use _pmb_select="..." instead of kernel variants (MR 2632)
2021-10-24 12:48:45 +00:00
depends="postmarketos-base mkbootimg linux-postmarketos-qcom-msm8916
soc-qcom-msm8916 soc-qcom-msm8916-rproc"
Initial support for Motorola Moto G4 Play (motorola-harpia) (#1437) Currently, Weston boots with a working touch interface, and USB networking.
2018-04-22 21:12:48 +00:00
makedepends="devicepkg-dev"
community/motorola-harpia: enable screen in initfs (MR 2110) As of MR 2039, the kernel modules are now stripped (INSTALL_MOD_STRIP=1). It turns out that this massively reduces their size so that including the panel + touchscreen modules in the initfs still fits into the boot partition. This allows the splash screen and osk-sdl to work correctly.
2021-04-11 18:10:17 +00:00
source="deviceinfo"
motorola-harpia: add option to enable modem (!958)
2020-02-04 11:41:38 +00:00
subpackages="
$pkgname-nonfree-firmware:nonfree_firmware
"
community/<msm8916>: use _pmb_select="..." instead of kernel variants (MR 2632)
2021-10-24 12:48:45 +00:00
_pmb_select="soc-qcom-msm8916-rproc"
# Backwards compatibility for old kernel variant subpackages
replaces="$pkgname-kernel-mainline $pkgname-kernel-mainline-modem"
for pkg in $replaces; do provides="$provides $pkg=$pkgver-r$pkgrel"; done
Initial support for Motorola Moto G4 Play (motorola-harpia) (#1437) Currently, Weston boots with a working touch interface, and USB networking.
2018-04-22 21:12:48 +00:00
build() {
devicepkg_build $startdir $pkgname
}
package() {
devicepkg_package $startdir $pkgname
}
motorola-harpia: upgrade to mainline kernel (!682) Support for the downstream kernel has been removed entirely. This is because the downstream kernel only has support for the armhf architecture, whereas linux-postmarketos-qcom-msm8916 is only built for aarch64. Since pmbootstrap has no way to handle having two kernels on differing architectures, the decision was made to remove the downstream kernel and only support mainline.
2019-10-13 11:00:28 +00:00
nonfree_firmware() {
<msm8916+secure boot+venus>: use separate firmware packages (MR 2619) Rule C: Devices with secure boot but without venus on the firmware partition need: 1. GPU firmware (firmware-qcom-adreno-a300) 2. msm-firmware-loader (for wcnss, modem) 4. device-specific -wcnss-nv firmware 5. device-specific -venus firmware
2021-10-19 08:31:47 +00:00
pkgdesc="GPU/WiFi/BT/Modem/Video firmware"
depends="firmware-qcom-adreno-a300 msm-firmware-loader
firmware-motorola-harpia-wcnss-nv firmware-motorola-harpia-venus"
motorola-harpia: add option to enable modem (!958)
2020-02-04 11:41:38 +00:00
mkdir "$subpkgdir"
}
device/*: set gpu_accelerated for devices that show '3D=Y' on wiki (MR 2078) [ci:ignore-count] [ci:skip-vercheck] needed for the postmarketos-ui-* packages in this series [ci:skip-build] already built ui-* packages in CI, and device pacakges are just trivial deviceinfo change (manually built some just to verify)
2021-07-07 05:06:17 +00:00
sha512sums="
community/<msm8916>: use _pmb_select="..." instead of kernel variants (MR 2632)
2021-10-24 12:48:45 +00:00
9cf557543fe876ae42298c2e717298cd03888fadf2d43a2794b1c7b3e13310796a914d59fade9b5421fc3035fd4b69b94b0bb75d30c559386f0cbfee98300bc3 deviceinfo
device/*: set gpu_accelerated for devices that show '3D=Y' on wiki (MR 2078) [ci:ignore-count] [ci:skip-vercheck] needed for the postmarketos-ui-* packages in this series [ci:skip-build] already built ui-* packages in CI, and device pacakges are just trivial deviceinfo change (manually built some just to verify)
2021-07-07 05:06:17 +00:00
"
Reference in a new issue Copy permalink