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

58 lines
2.3 KiB
Text
Raw Normal View History

motorola-osprey: restore firmware package (MR 3746) This reverts parts of commit 9c8a189e6d46429c365097029d329deb490afa09 ("motorola-osprey: use firmware from harpia (MR 2613)").
2022-12-17 13:54:55 +00:00
pkgname=firmware-motorola-osprey
firmware-<qcom-msm8916>: adjust for new venus firmware path (MR 4553) Linux 6.7-rc1 looks for the venus (video) firmware in qcom/venus-1.8/venus.mbn instead of qcom/venus-1.8/venus.mdt. Let's install it in both places with a symlink so that the firmware packages work for both older and newer Linux versions. [ci:ignore-count]: lots of packages [ci:skip-build] already built successfully in CI
2023-11-13 10:10:20 +00:00
pkgver=4
*/: Drop maintainership (MR 5302) Tweaked-by: Oliver Smith <ollieparanoid@postmarketos.org>
2024-06-30 21:38:09 +00:00
pkgrel=1
motorola-osprey: restore firmware package (MR 3746) This reverts parts of commit 9c8a189e6d46429c365097029d329deb490afa09 ("motorola-osprey: use firmware from harpia (MR 2613)").
2022-12-17 13:54:55 +00:00
pkgdesc="Firmware for Motorola Moto G 2015"
url="https://github.com/pmsourcedump/firmware-motorola-osprey"
firmware-motorola-osprey: package wcnss firmware for harpia (MR 3746) The WCNSS firwmare used for motorola-harpia seems to have weird issues that prevent using WiFi properly except for a few limited channels. It is not clear why this happens, it seems to be some peculiar firmware difference (perhaps the channels need to be enabled with some non-standard command). Since Motorola uses the same signing keys for all their MSM8916 devices, it is possible to use the firmware from other devices instead. Initial testing shows promising results when using the older WCNSS firmware from motorola-osprey instead, it does not seem to have this issue. It's not clear yet if this has any negative effects. The WCNSS firmware should not be device-specific, but theoretically it could be (if Motorola made some weird changes inside it). For now just package it in firmware-motorola-osprey-wcnss. This package can be easily installed on harpia devices for testing (using apk add) and will then take precendence over the default firmware from the firmware partition (via msm-firmware-loader). Move firmware-motorola-osprey from testing to community so that the package is preserved for motorola-harpia users (testing is deleted in stable branches). [ci:skip-build]: already built successfully in CI
2022-12-17 14:08:57 +00:00
subpackages="$pkgname-wcnss $pkgname-wcnss-nv:wcnss_nv $pkgname-venus"
motorola-osprey: restore firmware package (MR 3746) This reverts parts of commit 9c8a189e6d46429c365097029d329deb490afa09 ("motorola-osprey: use firmware from harpia (MR 2613)").
2022-12-17 13:54:55 +00:00
arch="aarch64"
license="proprietary"
options="!check !strip !archcheck !tracedeps pmb:cross-native"
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
makedepends="pil-squasher"
motorola-osprey: restore firmware package (MR 3746) This reverts parts of commit 9c8a189e6d46429c365097029d329deb490afa09 ("motorola-osprey: use firmware from harpia (MR 2613)").
2022-12-17 13:54:55 +00:00
_commit="a47c5a1c2dd806226c61305c9c97135f2734d0c7"
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
_muppets_commit="d2ff868a61c42ab84e85597600fe9e1064802c7b"
source="$pkgname-$_commit.tar.gz::https://github.com/pmsourcedump/firmware-motorola-osprey/archive/$_commit.tar.gz
WCNSS_qcom_wlan_nv_osprey.bin::https://github.com/TheMuppets/proprietary_vendor_motorola/raw/$_muppets_commit/osprey/proprietary/etc/firmware/wlan/prima/WCNSS_qcom_wlan_nv.bin"
builddir="$srcdir/firmware-motorola-osprey-$_commit"
motorola-osprey: restore firmware package (MR 3746) This reverts parts of commit 9c8a189e6d46429c365097029d329deb490afa09 ("motorola-osprey: use firmware from harpia (MR 2613)").
2022-12-17 13:54:55 +00:00
_fwdir="/lib/firmware/postmarketos"
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
build() {
firmware-motorola-osprey: package wcnss firmware for harpia (MR 3746) The WCNSS firwmare used for motorola-harpia seems to have weird issues that prevent using WiFi properly except for a few limited channels. It is not clear why this happens, it seems to be some peculiar firmware difference (perhaps the channels need to be enabled with some non-standard command). Since Motorola uses the same signing keys for all their MSM8916 devices, it is possible to use the firmware from other devices instead. Initial testing shows promising results when using the older WCNSS firmware from motorola-osprey instead, it does not seem to have this issue. It's not clear yet if this has any negative effects. The WCNSS firmware should not be device-specific, but theoretically it could be (if Motorola made some weird changes inside it). For now just package it in firmware-motorola-osprey-wcnss. This package can be easily installed on harpia devices for testing (using apk add) and will then take precendence over the default firmware from the firmware partition (via msm-firmware-loader). Move firmware-motorola-osprey from testing to community so that the package is preserved for motorola-harpia users (testing is deleted in stable branches). [ci:skip-build]: already built successfully in CI
2022-12-17 14:08:57 +00:00
pil-squasher wcnss.mbn wcnss.mdt
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
# venus.mbn exists already but seems a bit different
pil-squasher venus2.mbn venus.mdt
}
motorola-osprey: restore firmware package (MR 3746) This reverts parts of commit 9c8a189e6d46429c365097029d329deb490afa09 ("motorola-osprey: use firmware from harpia (MR 2613)").
2022-12-17 13:54:55 +00:00
package() {
mkdir -p "$pkgdir"
}
firmware-motorola-osprey: package wcnss firmware for harpia (MR 3746) The WCNSS firwmare used for motorola-harpia seems to have weird issues that prevent using WiFi properly except for a few limited channels. It is not clear why this happens, it seems to be some peculiar firmware difference (perhaps the channels need to be enabled with some non-standard command). Since Motorola uses the same signing keys for all their MSM8916 devices, it is possible to use the firmware from other devices instead. Initial testing shows promising results when using the older WCNSS firmware from motorola-osprey instead, it does not seem to have this issue. It's not clear yet if this has any negative effects. The WCNSS firmware should not be device-specific, but theoretically it could be (if Motorola made some weird changes inside it). For now just package it in firmware-motorola-osprey-wcnss. This package can be easily installed on harpia devices for testing (using apk add) and will then take precendence over the default firmware from the firmware partition (via msm-firmware-loader). Move firmware-motorola-osprey from testing to community so that the package is preserved for motorola-harpia users (testing is deleted in stable branches). [ci:skip-build]: already built successfully in CI
2022-12-17 14:08:57 +00:00
wcnss() {
pkgdesc="Motorola Moto G 2015 WiFi/BT firmware"
# Linux detects squashed (.mbn) vs non-squashed (.mdt + .b*) based on
firmware-<qcom-msm8916>: adjust for new venus firmware path (MR 4553) Linux 6.7-rc1 looks for the venus (video) firmware in qcom/venus-1.8/venus.mbn instead of qcom/venus-1.8/venus.mdt. Let's install it in both places with a symlink so that the firmware packages work for both older and newer Linux versions. [ci:ignore-count]: lots of packages [ci:skip-build] already built successfully in CI
2023-11-13 10:10:20 +00:00
# file contents, so it is fine to link wcnss.mbn to wcnss.mdt
install -Dm644 "$builddir"/wcnss.mbn "$subpkgdir/$_fwdir"/wcnss.mbn
ln -s wcnss.mbn "$subpkgdir/$_fwdir"/wcnss.mdt
firmware-motorola-osprey: package wcnss firmware for harpia (MR 3746) The WCNSS firwmare used for motorola-harpia seems to have weird issues that prevent using WiFi properly except for a few limited channels. It is not clear why this happens, it seems to be some peculiar firmware difference (perhaps the channels need to be enabled with some non-standard command). Since Motorola uses the same signing keys for all their MSM8916 devices, it is possible to use the firmware from other devices instead. Initial testing shows promising results when using the older WCNSS firmware from motorola-osprey instead, it does not seem to have this issue. It's not clear yet if this has any negative effects. The WCNSS firmware should not be device-specific, but theoretically it could be (if Motorola made some weird changes inside it). For now just package it in firmware-motorola-osprey-wcnss. This package can be easily installed on harpia devices for testing (using apk add) and will then take precendence over the default firmware from the firmware partition (via msm-firmware-loader). Move firmware-motorola-osprey from testing to community so that the package is preserved for motorola-harpia users (testing is deleted in stable branches). [ci:skip-build]: already built successfully in CI
2022-12-17 14:08:57 +00:00
}
motorola-osprey: restore firmware package (MR 3746) This reverts parts of commit 9c8a189e6d46429c365097029d329deb490afa09 ("motorola-osprey: use firmware from harpia (MR 2613)").
2022-12-17 13:54:55 +00:00
wcnss_nv() {
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
pkgdesc="Motorola Moto G 2015 WiFi/BT firmware configuration"
install -Dm644 "$srcdir"/WCNSS_qcom_wlan_nv_osprey.bin "$subpkgdir/$_fwdir"/wlan/prima/WCNSS_qcom_wlan_nv.bin
motorola-osprey: restore firmware package (MR 3746) This reverts parts of commit 9c8a189e6d46429c365097029d329deb490afa09 ("motorola-osprey: use firmware from harpia (MR 2613)").
2022-12-17 13:54:55 +00:00
}
venus() {
pkgdesc="Motorola Moto G 2015 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
# Linux detects squashed (.mbn) vs non-squashed (.mdt + .b*) based on
firmware-<qcom-msm8916>: adjust for new venus firmware path (MR 4553) Linux 6.7-rc1 looks for the venus (video) firmware in qcom/venus-1.8/venus.mbn instead of qcom/venus-1.8/venus.mdt. Let's install it in both places with a symlink so that the firmware packages work for both older and newer Linux versions. [ci:ignore-count]: lots of packages [ci:skip-build] already built successfully in CI
2023-11-13 10:10:20 +00:00
# file contents, so it is fine to link venus.mbn to venus.mdt
# Older kernels look for venus.mdt, newer ones directly for venus.mbn
install -Dm644 "$builddir"/venus2.mbn "$subpkgdir/$_fwdir"/qcom/venus-1.8/venus.mbn
ln -s venus.mbn "$subpkgdir/$_fwdir"/qcom/venus-1.8/venus.mdt
motorola-osprey: restore firmware package (MR 3746) This reverts parts of commit 9c8a189e6d46429c365097029d329deb490afa09 ("motorola-osprey: use firmware from harpia (MR 2613)").
2022-12-17 13:54:55 +00:00
}
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
sha512sums="
7e8d02baa8864c50b4a8be1f9af830e8b5440eee61a012725ed114d93012f0fb19ec005908832d3c96e0ba54b51a5ec7bcf137bfcc64c63594212f2497604629 firmware-motorola-osprey-a47c5a1c2dd806226c61305c9c97135f2734d0c7.tar.gz
1ee2e4f6eb3662b0f6b6034313d30a81d48dab78680ccd5f3c84ca023719e2c6021b2dbec79468719dc01e27b53b76e1097c9ed5edc476b601c4fd1d80373a7a WCNSS_qcom_wlan_nv_osprey.bin
"
Reference in a new issue Copy permalink