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

57 lines
1.8 KiB
Text
Raw Normal View History

Add device: wileyfox-crackling (!485) Initial support for Wileyfox Swift - System boots - USB networking works - Display and touch works - Weston, XFCE4, Plasma Mobile works with software rendering - fb.modes added but charging-sdl still don't work - System allways reports charge level at zero [ci:skip-build]: already built successfully in CI
2019-07-08 18:20:20 +00:00
# Reference: <https://postmarketos.org/devicepkg>
wileyfox-crackling: move from testing to community (MR 1273)
2020-05-27 04:33:49 +00:00
# Maintainer: Nikita Travkin <nikitos.tr@gmail.com>
treewide: avoid "More than one maintainer" error (MR 1480) Alpine's abuild is soon going to complain if an APKBUILD has more than one "Maintainer:" listed. Work around it by renaming the additional maintainers to "Co-Maintainer:". While at it, move the devicepkg reference link to the top in device-xiaomi-santoni for consistency. In postmarketOS, we require at least two maintainers for devices in main, therefore it does not make sense to drop additional maintainers from the file. In Alpine, this change was made because pkgs.alpinelinux.org apparently can't handle more than one maintainer. I looked into it, and it would require a database change to add it there, so it does not seem worth the effort. I also thought about extending abuild to add an environment variable to skip the check, but then the package would not build with plain abuild without using the env var. Related: https://gitlab.alpinelinux.org/alpine/abuild/-/commit/dd4cd9d606f5e28f382414e258af562e346c6ab5 [ci:skip-build] [ci:skip-vercheck]
2020-08-04 09:46:27 +00:00
# Co-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-wileyfox-crackling
Add device: wileyfox-crackling (!485) Initial support for Wileyfox Swift - System boots - USB networking works - Display and touch works - Weston, XFCE4, Plasma Mobile works with software rendering - fb.modes added but charging-sdl still don't work - System allways reports charge level at zero [ci:skip-build]: already built successfully in CI
2019-07-08 18:20:20 +00:00
pkgdesc="Wileyfox Swift"
device/device-<msm8916-mainline>: minor cleanup and fixes (MR 1125) - Cleanup kernel cmdline: - earlycon can automatically detect the memory address of the UART controller based on the device tree - the comma before n8 in console=ttyMSM0,115200,n8 is actually invalid so this was not parsed correctly. However, it is the default anyway so we might as well remove it completely - Configure deviceinfo_getty for all devices - Workaround probe issue of display by adding a softdep on the panel module. This allows the display to work when excluding proprietary firmware (just a weird side effect, see comment in modprobe.conf...)
2020-04-04 16:00:14 +00:00
pkgver=3
device/*: Add deviceinfo_chassis variable (MR 1246) [ci:ignore-count], [ci:skip-build]
2020-05-17 13:33:49 +00:00
pkgrel=1
Add device: wileyfox-crackling (!485) Initial support for Wileyfox Swift - System boots - USB networking works - Display and touch works - Weston, XFCE4, Plasma Mobile works with software rendering - fb.modes added but charging-sdl still don't work - System allways reports charge level at zero [ci:skip-build]: already built successfully in CI
2019-07-08 18:20:20 +00:00
url="https://postmarketos.org"
license="MIT"
arch="aarch64"
options="!check !archcheck"
wileyfox-crackling: remove downstream kernel (MR 1125) The device port gets increasingly hard to maintain with all the differences between the downstream and the mainline kernel. Especially deviceinfo has quite some duplication only because the downstream kernel needs to be handled as well. The mainline port has much more features working. The only limitation compared to the downstream kernel is the lack of a proper charging driver. But even on downstream postmarketOS the battery driver is not working properly for some reason. For charging, a downstream installation in recovery seems more suitable at the moment. Eventually we will build some functionality into the bootloader to load a simple downstream initramfs when the device gets booted for charging.
2020-04-04 15:50:19 +00:00
depends="postmarketos-base mkbootimg soc-qcom-msm8916"
Add device: wileyfox-crackling (!485) Initial support for Wileyfox Swift - System boots - USB networking works - Display and touch works - Weston, XFCE4, Plasma Mobile works with software rendering - fb.modes added but charging-sdl still don't work - System allways reports charge level at zero [ci:skip-build]: already built successfully in CI
2019-07-08 18:20:20 +00:00
makedepends="devicepkg-dev"
device/device-<msm8916-mainline>: minor cleanup and fixes (MR 1125) - Cleanup kernel cmdline: - earlycon can automatically detect the memory address of the UART controller based on the device tree - the comma before n8 in console=ttyMSM0,115200,n8 is actually invalid so this was not parsed correctly. However, it is the default anyway so we might as well remove it completely - Configure deviceinfo_getty for all devices - Workaround probe issue of display by adding a softdep on the panel module. This allows the display to work when excluding proprietary firmware (just a weird side effect, see comment in modprobe.conf...)
2020-04-04 16:00:14 +00:00
source="deviceinfo modprobe.conf"
wileyfox-crackling: add mainline kernel (!582) [ci:skip-build]: already built successfully in CI
2019-07-12 19:42:56 +00:00
subpackages="
$pkgname-kernel-mainline:kernel_mainline
wileyfox-crackling: add option to enable modem (!907)
2020-01-18 11:40:15 +00:00
$pkgname-kernel-mainline-modem:kernel_mainline_modem
wileyfox-crackling: add mainline kernel (!582) [ci:skip-build]: already built successfully in CI
2019-07-12 19:42:56 +00:00
$pkgname-nonfree-firmware:nonfree_firmware
wileyfox-crackling: add option to enable modem (!907)
2020-01-18 11:40:15 +00:00
$pkgname-nonfree-firmware-modem:nonfree_firmware_modem
wileyfox-crackling: add mainline kernel (!582) [ci:skip-build]: already built successfully in CI
2019-07-12 19:42:56 +00:00
"
Add device: wileyfox-crackling (!485) Initial support for Wileyfox Swift - System boots - USB networking works - Display and touch works - Weston, XFCE4, Plasma Mobile works with software rendering - fb.modes added but charging-sdl still don't work - System allways reports charge level at zero [ci:skip-build]: already built successfully in CI
2019-07-08 18:20:20 +00:00
build() {
devicepkg_build $startdir $pkgname
}
package() {
devicepkg_package $startdir $pkgname
wileyfox-crackling: add mainline kernel (!582) [ci:skip-build]: already built successfully in CI
2019-07-12 19:42:56 +00:00
}
kernel_mainline() {
device/*: clarify "close to mainline" (cosmetic) (MR 1408) Make it clear, that these kernels are not mainline, but "close to mainline". [ci:skip-build] [ci:skip-vercheck]: just changing pkgdesc Related: https://wiki.postmarketos.org/wiki/(Close_to)_Mainline
2020-07-11 09:16:39 +00:00
pkgdesc="Close to mainline kernel (no charging, no modem, audio routed directly)"
wileyfox-crackling: remove downstream kernel (MR 1125) The device port gets increasingly hard to maintain with all the differences between the downstream and the mainline kernel. Especially deviceinfo has quite some duplication only because the downstream kernel needs to be handled as well. The mainline port has much more features working. The only limitation compared to the downstream kernel is the lack of a proper charging driver. But even on downstream postmarketOS the battery driver is not working properly for some reason. For charging, a downstream installation in recovery seems more suitable at the moment. Eventually we will build some functionality into the bootloader to load a simple downstream initramfs when the device gets booted for charging.
2020-04-04 15:50:19 +00:00
depends="linux-postmarketos-qcom-msm8916"
wileyfox-crackling: add mainline kernel (!582) [ci:skip-build]: already built successfully in CI
2019-07-12 19:42:56 +00:00
devicepkg_subpackage_kernel $startdir $pkgname $subpkgname
}
wileyfox-crackling: add option to enable modem (!907)
2020-01-18 11:40:15 +00:00
kernel_mainline_modem() {
device/*: clarify "close to mainline" (cosmetic) (MR 1408) Make it clear, that these kernels are not mainline, but "close to mainline". [ci:skip-build] [ci:skip-vercheck]: just changing pkgdesc Related: https://wiki.postmarketos.org/wiki/(Close_to)_Mainline
2020-07-11 09:16:39 +00:00
pkgdesc="Close to mainline kernel (no charging, non-free modem, audio routed through ADSP)"
wileyfox-crackling: remove downstream kernel (MR 1125) The device port gets increasingly hard to maintain with all the differences between the downstream and the mainline kernel. Especially deviceinfo has quite some duplication only because the downstream kernel needs to be handled as well. The mainline port has much more features working. The only limitation compared to the downstream kernel is the lack of a proper charging driver. But even on downstream postmarketOS the battery driver is not working properly for some reason. For charging, a downstream installation in recovery seems more suitable at the moment. Eventually we will build some functionality into the bootloader to load a simple downstream initramfs when the device gets booted for charging.
2020-04-04 15:50:19 +00:00
depends="linux-postmarketos-qcom-msm8916 soc-qcom-msm8916-modem"
wileyfox-crackling: add mainline kernel (!582) [ci:skip-build]: already built successfully in CI
2019-07-12 19:42:56 +00:00
devicepkg_subpackage_kernel $startdir $pkgname $subpkgname
}
nonfree_firmware() {
wileyfox-crackling: add option to enable modem (!907)
2020-01-18 11:40:15 +00:00
pkgdesc="GPU/WiFi/BT/Video(/Modem) firmware"
wileyfox-crackling: add mainline kernel (!582) [ci:skip-build]: already built successfully in CI
2019-07-12 19:42:56 +00:00
depends="linux-firmware-qcom firmware-wileyfox-crackling-venus firmware-wileyfox-crackling-wcnss"
mkdir "$subpkgdir"
Add device: wileyfox-crackling (!485) Initial support for Wileyfox Swift - System boots - USB networking works - Display and touch works - Weston, XFCE4, Plasma Mobile works with software rendering - fb.modes added but charging-sdl still don't work - System allways reports charge level at zero [ci:skip-build]: already built successfully in CI
2019-07-08 18:20:20 +00:00
}
wileyfox-crackling: add option to enable modem (!907)
2020-01-18 11:40:15 +00:00
nonfree_firmware_modem() {
pkgdesc="Modem firmware"
depends="firmware-wileyfox-crackling-modem"
install_if="$pkgname-nonfree-firmware $pkgname-kernel-mainline-modem"
mkdir "$subpkgdir"
}
device/*: Add deviceinfo_chassis variable (MR 1246) [ci:ignore-count], [ci:skip-build]
2020-05-17 13:33:49 +00:00
sha512sums="2b2b3ca29bfbe70c47550de1736595b7b613a34728e2339e45baa3188615531cca17690b6c85118aecc0dcc695a1586f49a806663eea841612b17ef7a1ca595c deviceinfo
device/device-<msm8916-mainline>: minor cleanup and fixes (MR 1125) - Cleanup kernel cmdline: - earlycon can automatically detect the memory address of the UART controller based on the device tree - the comma before n8 in console=ttyMSM0,115200,n8 is actually invalid so this was not parsed correctly. However, it is the default anyway so we might as well remove it completely - Configure deviceinfo_getty for all devices - Workaround probe issue of display by adding a softdep on the panel module. This allows the display to work when excluding proprietary firmware (just a weird side effect, see comment in modprobe.conf...)
2020-04-04 16:00:14 +00:00
a033c958c7539c7f2ce0b1f5ee3977900f8a71a02e9ff5e7f32aaeb7e3687e1765034a7c30477c050e3e0af67e534ecc2984eecbfce34c689247c24f69149d27 modprobe.conf"
Reference in a new issue Copy permalink