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

40 lines
1.1 KiB
Text
Raw Normal View History

device/device-motorola-osprey: fix APKBUILD (!874)
2020-01-10 16:31:33 +00:00
# Reference: <https://postmarketos.org/devicepkg>
Device motorola-osprey (#714)
2017-10-07 17:55:55 +00:00
pkgname=device-motorola-osprey
device/msm8916*: Generate extlinux.conf (MR 4826) Now as boot-deploy allows us to generate both boot.img and extlinux.conf at the same time, enable generating the config for all msm8916 since it will be used in the future lk2nd release. boot.img is still kept to keep compatibility with current lk2nd releases and to allow system recovery with fastboot when required. [ci:skip-build] already built successfully in CI [ci:ignore-count]
2024-02-15 08:21:05 +00:00
pkgver=8
pkgrel=0
motorola-osprey: rename to Motorola Moto G 2015 (MR 3746) motorola-osprey has a very clunky name at the moment "Motorola Moto G 3rd gen. (2015)". The device was mostly just called "Motorola Moto G" by Motorola, so it is hard to choose a fitting (but unique) name. In the postmarketOS wiki it is called "Motorola Moto G 2015" so let's just drop the "3rd gen." in the pmOS device package as well. Also make the deviceinfo consistent with harpia while at it.
2022-12-17 12:50:32 +00:00
pkgdesc="Motorola Moto G 2015"
Remove github.com references * Travis and Coveralls badges * aports: instead of <https://github.com/postmarketOS>, use <https://postmarketos.org> * References to full URLs to issues and pull requests replaced with a hash and the number * grsec check: simplify error message, remove link to github issue (nobody is using that anymore anyway)
2018-06-30 07:00:48 +00:00
url="https://postmarketos.org"
device/motorola-osprey: switch to mainline (MR 1872)
2020-12-17 12:10:10 +00:00
arch="aarch64"
Device motorola-osprey (#714)
2017-10-07 17:55:55 +00:00
license="MIT"
testing/<msm8916>: use _pmb_select="..." instead of kernel variants (MR 2632)
2021-10-29 15:29:18 +00:00
depends="postmarketos-base mkbootimg linux-postmarketos-qcom-msm8916
soc-qcom-msm8916 soc-qcom-msm8916-rproc"
device/device-motorola-osprey: fix APKBUILD (!874)
2020-01-10 16:31:33 +00:00
makedepends="devicepkg-dev"
device/*: transform deviceinfo_modules_initfs into a file (MR 4169) The file is automatically packed by devicepkg-dev utils Relates #1836
2023-08-02 17:06:01 +00:00
source="deviceinfo modules-initfs"
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"
testing/<msm8916>: use _pmb_select="..." instead of kernel variants (MR 2632)
2021-10-29 15:29:18 +00:00
_pmb_select="soc-qcom-msm8916-rproc"
Device motorola-osprey (#714)
2017-10-07 17:55:55 +00:00
device/motorola-osprey: switch to mainline (MR 1872)
2020-12-17 12:10:10 +00:00
subpackages="
$pkgname-nonfree-firmware:nonfree_firmware
"
device/device-motorola-osprey: fix APKBUILD (!874)
2020-01-10 16:31:33 +00:00
build() {
devicepkg_build $startdir $pkgname
}
Device motorola-osprey (#714)
2017-10-07 17:55:55 +00:00
package() {
device/device-motorola-osprey: fix APKBUILD (!874)
2020-01-10 16:31:33 +00:00
devicepkg_package $startdir $pkgname
Device motorola-osprey (#714)
2017-10-07 17:55:55 +00:00
}
device/motorola-osprey: switch to mainline (MR 1872)
2020-12-17 12:10:10 +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"
motorola-osprey: use device-specific WCNSS_qcom_wlan_nv.bin (MR 3746) motorola-osprey can generally use the firmware from motorola-harpia (which is a bit newer). However, the WCNSS_qcom_wlan_nv.bin is usually device specific (it contains some kind of calibration values for WiFi/BT). The file packaged in firmware-motorola-osprey-wcnss-nv is identical to the file in firmware-motorola-harpia-wcnss-nv. However, It looks a bit like this might be a mistake in the source repository (https://github.com/pmsourcedump/firmware-motorola-osprey). The wlan/prima folder there is completely identical to the one used for motorola-harpia, but the stock ROM and LineageOS use different files. Fix this by packaging the file from TheMuppets. Also modernize the firmware-motorola-osprey package by applying pil-squasher to the venus/video firmware.
2022-12-17 14:02:31 +00:00
# osprey can use newer venus firmware from harpia
<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
depends="firmware-qcom-adreno-a300 msm-firmware-loader
motorola-osprey: use device-specific WCNSS_qcom_wlan_nv.bin (MR 3746) motorola-osprey can generally use the firmware from motorola-harpia (which is a bit newer). However, the WCNSS_qcom_wlan_nv.bin is usually device specific (it contains some kind of calibration values for WiFi/BT). The file packaged in firmware-motorola-osprey-wcnss-nv is identical to the file in firmware-motorola-harpia-wcnss-nv. However, It looks a bit like this might be a mistake in the source repository (https://github.com/pmsourcedump/firmware-motorola-osprey). The wlan/prima folder there is completely identical to the one used for motorola-harpia, but the stock ROM and LineageOS use different files. Fix this by packaging the file from TheMuppets. Also modernize the firmware-motorola-osprey package by applying pil-squasher to the venus/video firmware.
2022-12-17 14:02:31 +00:00
firmware-motorola-osprey-wcnss-nv firmware-motorola-harpia-venus"
device/motorola-osprey: switch to mainline (MR 1872)
2020-12-17 12:10:10 +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="
device/msm8916*: Generate extlinux.conf (MR 4826) Now as boot-deploy allows us to generate both boot.img and extlinux.conf at the same time, enable generating the config for all msm8916 since it will be used in the future lk2nd release. boot.img is still kept to keep compatibility with current lk2nd releases and to allow system recovery with fastboot when required. [ci:skip-build] already built successfully in CI [ci:ignore-count]
2024-02-15 08:21:05 +00:00
9f947bef8c8f90924f1e087a6f9443d7739546c8971b855ebee2c0fd0437d26ab45feaf2f6f7c38db98831e3f16b19020d945d1f580d974a6d7597723e7d072b deviceinfo
device/*: transform deviceinfo_modules_initfs into a file (MR 4169) The file is automatically packed by devicepkg-dev utils Relates #1836
2023-08-02 17:06:01 +00:00
fc1d1e57bd2a366884b1359ba32acfb484719958fb655067cfba28787384d626dde7683750dda523e2941df4fc78e2d234130ef5a5217002a09623a4a2f34919 modules-initfs
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