forge/pmaports
1
0
Fork 0
Code Issues 2 Pull requests Projects Releases Packages Wiki Activity Actions
pmaports/main/msm-firmware-loader/APKBUILD

48 lines
1.7 KiB
Text
Raw Normal View History

main/msm-firmware-loader: add a package to load firmware on msm devices (MR 2431) Many devices need proprietary firmware blobs. So far those blobs were packaged and installed from the repository but this approach has many drawbacks: - The rootfs can only be used on a single device model. - If a model has multiple variants that have diferent secire-boot key, each must have it's own firmware blobs. This makes maintaining packaged firmware very hard and outweights the benefits of having a repeatable installation in most cases. Instead we can load blobs dynamically from preexisting firmware partitions that usually have same structure and contain the blobs we are interested in. The proposed scripts place symlinks to the blobs in a special dir that then given to the kernel. Blobs from firmware/postmarketos (or another dir that was set as extra path prior the script execution) will take priority which allows to override some blobs (e.g. for deviecs with no secure-boot)
2021-08-04 11:05:49 +00:00
pkgname=msm-firmware-loader
main/msm-firmware-loader: upgrade to 1.3.0 (MR 4448) [ci:skip-build]: already built successfully in CI
2023-10-04 18:49:05 +00:00
pkgver=1.3.0
main/msm-firmware-loader: upgrade to 1.1.0 (MR 3797) [ci:skip-build]: already built successfully in CI
2023-01-10 10:35:55 +00:00
pkgrel=0
main/msm-firmware-loader: add a package to load firmware on msm devices (MR 2431) Many devices need proprietary firmware blobs. So far those blobs were packaged and installed from the repository but this approach has many drawbacks: - The rootfs can only be used on a single device model. - If a model has multiple variants that have diferent secire-boot key, each must have it's own firmware blobs. This makes maintaining packaged firmware very hard and outweights the benefits of having a repeatable installation in most cases. Instead we can load blobs dynamically from preexisting firmware partitions that usually have same structure and contain the blobs we are interested in. The proposed scripts place symlinks to the blobs in a special dir that then given to the kernel. Blobs from firmware/postmarketos (or another dir that was set as extra path prior the script execution) will take priority which allows to override some blobs (e.g. for deviecs with no secure-boot)
2021-08-04 11:05:49 +00:00
pkgdesc="Set of init services to automatically load firmware from device partitions"
url="https://postmarketos.org/"
main/msm-firmware-loader: add dummy wcnss subpackage (MR 2619) firmware-qcom-msm8916-wcnss is a virtual package used for MSM8916 devices without secure boot (i.e. device that do not require signed firmware). For those it's best to install more recent firmware by default rather than using the firmware on the firmware partition. firmware-qcom-msm8916-wcnss is provided by firmware-qcom-db410c-wcnss by default, however it's still useful to make it possible to switch to the stock firmware on the firmware partition if needed. To allow that, add a dummy msm-firmware-loader-wcnss package that provides the virtual package using the msm-firmware-loader. # apk add msm-firmware-loader-wcnss (1/2) Purging firmware-qcom-db410c-wcnss (1034.2.1-r2) (2/2) Installing msm-firmware-loader-wcnss (1-r1)
2021-10-19 07:44:31 +00:00
subpackages="$pkgname-wcnss"
main/msm-firmware-loader: add a package to load firmware on msm devices (MR 2431) Many devices need proprietary firmware blobs. So far those blobs were packaged and installed from the repository but this approach has many drawbacks: - The rootfs can only be used on a single device model. - If a model has multiple variants that have diferent secire-boot key, each must have it's own firmware blobs. This makes maintaining packaged firmware very hard and outweights the benefits of having a repeatable installation in most cases. Instead we can load blobs dynamically from preexisting firmware partitions that usually have same structure and contain the blobs we are interested in. The proposed scripts place symlinks to the blobs in a special dir that then given to the kernel. Blobs from firmware/postmarketos (or another dir that was set as extra path prior the script execution) will take priority which allows to override some blobs (e.g. for deviecs with no secure-boot)
2021-08-04 11:05:49 +00:00
arch="armhf armv7 aarch64"
license="MIT"
install="$pkgname.post-install"
source="
main/msm-firmware-loader: use separate repo as source (MR 3260) Closes https://gitlab.com/postmarketOS/pmaports/-/issues/1292
2022-06-28 18:32:21 +00:00
https://gitlab.com/postmarketOS/msm-firmware-loader/-/archive/$pkgver/msm-firmware-loader-$pkgver.tar.gz
main/msm-firmware-loader: add a package to load firmware on msm devices (MR 2431) Many devices need proprietary firmware blobs. So far those blobs were packaged and installed from the repository but this approach has many drawbacks: - The rootfs can only be used on a single device model. - If a model has multiple variants that have diferent secire-boot key, each must have it's own firmware blobs. This makes maintaining packaged firmware very hard and outweights the benefits of having a repeatable installation in most cases. Instead we can load blobs dynamically from preexisting firmware partitions that usually have same structure and contain the blobs we are interested in. The proposed scripts place symlinks to the blobs in a special dir that then given to the kernel. Blobs from firmware/postmarketos (or another dir that was set as extra path prior the script execution) will take priority which allows to override some blobs (e.g. for deviecs with no secure-boot)
2021-08-04 11:05:49 +00:00
msm-firmware-loader.initd
msm-firmware-loader-unpack.initd
"
options="!check"
package() {
mkdir -p "$pkgdir"
install -Dm755 "$srcdir/msm-firmware-loader.initd" \
"$pkgdir/etc/init.d/msm-firmware-loader"
install -Dm755 "$srcdir/msm-firmware-loader-unpack.initd" \
"$pkgdir/etc/init.d/msm-firmware-loader-unpack"
# Create mountpoint for the scripts
mkdir -p "$pkgdir/lib/firmware/msm-firmware-loader"
main/msm-firmware-loader: use separate repo as source (MR 3260) Closes https://gitlab.com/postmarketOS/pmaports/-/issues/1292
2022-06-28 18:32:21 +00:00
install -Dm755 msm-firmware-loader.sh \
main/msm-firmware-loader: add a package to load firmware on msm devices (MR 2431) Many devices need proprietary firmware blobs. So far those blobs were packaged and installed from the repository but this approach has many drawbacks: - The rootfs can only be used on a single device model. - If a model has multiple variants that have diferent secire-boot key, each must have it's own firmware blobs. This makes maintaining packaged firmware very hard and outweights the benefits of having a repeatable installation in most cases. Instead we can load blobs dynamically from preexisting firmware partitions that usually have same structure and contain the blobs we are interested in. The proposed scripts place symlinks to the blobs in a special dir that then given to the kernel. Blobs from firmware/postmarketos (or another dir that was set as extra path prior the script execution) will take priority which allows to override some blobs (e.g. for deviecs with no secure-boot)
2021-08-04 11:05:49 +00:00
"$pkgdir/usr/sbin/msm-firmware-loader.sh"
main/msm-firmware-loader: use separate repo as source (MR 3260) Closes https://gitlab.com/postmarketOS/pmaports/-/issues/1292
2022-06-28 18:32:21 +00:00
install -Dm755 msm-firmware-loader-unpack.sh \
main/msm-firmware-loader: add a package to load firmware on msm devices (MR 2431) Many devices need proprietary firmware blobs. So far those blobs were packaged and installed from the repository but this approach has many drawbacks: - The rootfs can only be used on a single device model. - If a model has multiple variants that have diferent secire-boot key, each must have it's own firmware blobs. This makes maintaining packaged firmware very hard and outweights the benefits of having a repeatable installation in most cases. Instead we can load blobs dynamically from preexisting firmware partitions that usually have same structure and contain the blobs we are interested in. The proposed scripts place symlinks to the blobs in a special dir that then given to the kernel. Blobs from firmware/postmarketos (or another dir that was set as extra path prior the script execution) will take priority which allows to override some blobs (e.g. for deviecs with no secure-boot)
2021-08-04 11:05:49 +00:00
"$pkgdir/usr/sbin/msm-firmware-loader-unpack.sh"
}
main/msm-firmware-loader: add dummy wcnss subpackage (MR 2619) firmware-qcom-msm8916-wcnss is a virtual package used for MSM8916 devices without secure boot (i.e. device that do not require signed firmware). For those it's best to install more recent firmware by default rather than using the firmware on the firmware partition. firmware-qcom-msm8916-wcnss is provided by firmware-qcom-db410c-wcnss by default, however it's still useful to make it possible to switch to the stock firmware on the firmware partition if needed. To allow that, add a dummy msm-firmware-loader-wcnss package that provides the virtual package using the msm-firmware-loader. # apk add msm-firmware-loader-wcnss (1/2) Purging firmware-qcom-db410c-wcnss (1034.2.1-r2) (2/2) Installing msm-firmware-loader-wcnss (1-r1)
2021-10-19 07:44:31 +00:00
wcnss() {
pkgdesc="Use WiFi/BT firmware from stock firmware partition using $pkgname"
main/msm-firmware-loader: fix provides (MR 3597)
2022-10-30 13:04:44 +00:00
provides="firmware-qcom-msm8916-wcnss=$pkgver-r$pkgrel"
main/msm-firmware-loader: add dummy wcnss subpackage (MR 2619) firmware-qcom-msm8916-wcnss is a virtual package used for MSM8916 devices without secure boot (i.e. device that do not require signed firmware). For those it's best to install more recent firmware by default rather than using the firmware on the firmware partition. firmware-qcom-msm8916-wcnss is provided by firmware-qcom-db410c-wcnss by default, however it's still useful to make it possible to switch to the stock firmware on the firmware partition if needed. To allow that, add a dummy msm-firmware-loader-wcnss package that provides the virtual package using the msm-firmware-loader. # apk add msm-firmware-loader-wcnss (1/2) Purging firmware-qcom-db410c-wcnss (1034.2.1-r2) (2/2) Installing msm-firmware-loader-wcnss (1-r1)
2021-10-19 07:44:31 +00:00
depends="$pkgname"
# empty package, just some magic
mkdir -p "$subpkgdir"
}
main/msm-firmware-loader: add a package to load firmware on msm devices (MR 2431) Many devices need proprietary firmware blobs. So far those blobs were packaged and installed from the repository but this approach has many drawbacks: - The rootfs can only be used on a single device model. - If a model has multiple variants that have diferent secire-boot key, each must have it's own firmware blobs. This makes maintaining packaged firmware very hard and outweights the benefits of having a repeatable installation in most cases. Instead we can load blobs dynamically from preexisting firmware partitions that usually have same structure and contain the blobs we are interested in. The proposed scripts place symlinks to the blobs in a special dir that then given to the kernel. Blobs from firmware/postmarketos (or another dir that was set as extra path prior the script execution) will take priority which allows to override some blobs (e.g. for deviecs with no secure-boot)
2021-08-04 11:05:49 +00:00
sha512sums="
main/msm-firmware-loader: upgrade to 1.3.0 (MR 4448) [ci:skip-build]: already built successfully in CI
2023-10-04 18:49:05 +00:00
7320a2c363b5e80459c5dcf1933d671c0aacf519c5e8084a07e126f3b0f7747926495b231f7494566971ccf9732ae8af0d3bc1ee49a1d8d176024c3610aa288f msm-firmware-loader-1.3.0.tar.gz
main/msm-firmware-loader: add a package to load firmware on msm devices (MR 2431) Many devices need proprietary firmware blobs. So far those blobs were packaged and installed from the repository but this approach has many drawbacks: - The rootfs can only be used on a single device model. - If a model has multiple variants that have diferent secire-boot key, each must have it's own firmware blobs. This makes maintaining packaged firmware very hard and outweights the benefits of having a repeatable installation in most cases. Instead we can load blobs dynamically from preexisting firmware partitions that usually have same structure and contain the blobs we are interested in. The proposed scripts place symlinks to the blobs in a special dir that then given to the kernel. Blobs from firmware/postmarketos (or another dir that was set as extra path prior the script execution) will take priority which allows to override some blobs (e.g. for deviecs with no secure-boot)
2021-08-04 11:05:49 +00:00
d9ad3b21564de9a4970a8923b8598fb46a54543ac9f1494676a6833800bc68c64f230737b308fec54aae09c2cf635794e8f1abc46253b0386260b4580587483d msm-firmware-loader.initd
616a28c3a65a45bb65f798989d93daacdeea08a90a9a8538b5bac2d73b2c8b135554ecaf49b4084829f88af760a144802adcd89b50f46bc267d6b04c9c733ff8 msm-firmware-loader-unpack.initd
"
Reference in a new issue Copy permalink