pmaports/device/device-wileyfox-crackling/APKBUILD
Minecrell eec966d19f
wileyfox-crackling: use appended DTB instead of QCDT (!907)
The Wileyfox Swift is the only mainline MSM8916 device using QCDT
at the moment. The other devices do not have unique qcom,board-ids
that could be used within QCDT.

So far this has worked fine for the Wileyfox Swift. However,
in preparation to *optionally* load the modem we now need two separate
pairs of DTBs (one with modem and one without modem). This is simple
to implement using appended DTBs, but not possible with QCDT.

So let's stop using QCDT entirely for mainline,
and use appended DTBs for wileyfox-crackling.
2020-02-16 12:47:36 +01:00

52 lines
1.5 KiB
Text

# Reference: <https://postmarketos.org/devicepkg>
# Contributor: Nikita Travkin <nikitos.tr@gmail.com>
pkgname="device-wileyfox-crackling"
pkgdesc="Wileyfox Swift"
pkgver=1
pkgrel=4
url="https://postmarketos.org"
license="MIT"
arch="aarch64"
options="!check !archcheck"
depends="postmarketos-base mkbootimg"
makedepends="devicepkg-dev"
subpackages="
$pkgname-kernel-mainline:kernel_mainline
$pkgname-kernel-downstream:kernel_downstream
$pkgname-nonfree-firmware:nonfree_firmware
"
source="
deviceinfo
fb.modes
"
build() {
devicepkg_build $startdir $pkgname
}
package() {
devicepkg_package $startdir $pkgname
install -Dm544 "$srcdir"/fb.modes "$pkgdir"/etc/fb.modes
}
kernel_mainline() {
pkgdesc="Most features working (note: charging not working yet)"
depends="linux-postmarketos-qcom-msm8916 soc-qcom-msm8916"
devicepkg_subpackage_kernel $startdir $pkgname $subpkgname
}
kernel_downstream() {
pkgdesc="For charging/debugging only (prefer mainline)"
depends="linux-wileyfox-crackling mesa-dri-swrast mdss-fb-init-hack"
devicepkg_subpackage_kernel $startdir $pkgname $subpkgname
}
nonfree_firmware() {
pkgdesc="GPU/WiFi/BT/Video firmware"
depends="linux-firmware-qcom firmware-wileyfox-crackling-venus firmware-wileyfox-crackling-wcnss"
mkdir "$subpkgdir"
}
sha512sums="904e1080dc42bbf438b13d4cec7871425ec39c9f33700276849f43c0f4504902c4873f31be0cb027407062689ba85a1b03136d9d73b44ae392d0474378418598 deviceinfo
587be41a15f5738c6f55c52f760e08810185a00af886e84864f77ce38675bdf65893779a4ea88c9811023746895818ce5829a1b060e158f2cdae87d13e13f07d fb.modes"