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

69 lines
2.1 KiB
Text
Raw Normal View History

device/pine64-{pinebookpro,rockpro64}: new device (MR 882) [ci:skip-build]
2020-04-07 17:56:30 +00:00
# Reference: <https://postmarketos.org/devicepkg>
device-pine64-pinebookpro: add Clayton as maintainer (MR 2352)
2021-07-18 01:52:41 +00:00
# Maintainer: Clayton Craft <clayton@craftyguy.net>
device/pine64-{pinebookpro,rockpro64}: new device (MR 882) [ci:skip-build]
2020-04-07 17:56:30 +00:00
pkgname=device-pine64-pinebookpro
pkgdesc="PINE64 Pinebook Pro"
device-pine64-pinebookpro: Enable s2idle in elogind. (MR 4194) [ci:skip-build]: already built successfully in CI
2023-06-20 02:56:42 +00:00
pkgver=16
pine64-pinebookpro: depend on soc-rockchip-rk3399 (MR 4337)
2023-08-18 23:26:05 +00:00
pkgrel=3
device/pine64-{pinebookpro,rockpro64}: new device (MR 882) [ci:skip-build]
2020-04-07 17:56:30 +00:00
url="https://postmarketos.org"
license="MIT"
arch="aarch64"
options="!check !archcheck"
pine64-pinebookpro: add service for setting low power state on boot (MR 2306) This adds a very basic openrc runscript that sets the power state on /dev/nvme0 to level 2, which seems(?) to be the lowest operational power state based on some cursory internet searching (and querying the nvme drives I have, Samsung EVO and Pro) The drive path is hard coded, but could be made configurable later on. I basically wanted to get something in pmaports quickly, since this power stuff is a major source of instability for me and probably others too who add nvme drives to this device.
2021-07-04 00:38:55 +00:00
depends="
device-pine64-pinebookpro: drop ALSA UCM configs (MR 3268) ALSA UCM configs are now upstreamed which causes a conflict with the device package as both are now providing the same files. Drop our configs in the device package.
2022-07-01 12:21:42 +00:00
alsa-ucm-conf>=1.2.7
pine64-pinebookpro: switch to upstream udev rules (MR 4095) The entries kept locally are now part of the upstream rules. We can rely on those instead and avoid the duplication. See: https://github.com/eudev-project/eudev/blob/2703baf55615b7554fb67c4f1c241f057f8c0a79/hwdb/60-evdev.hwdb#L625 See: https://github.com/eudev-project/eudev/blob/2703baf55615b7554fb67c4f1c241f057f8c0a79/hwdb/60-keyboard.hwdb#L1526 [ci:skip-build]: already built successfully in CI
2023-05-19 09:26:06 +00:00
eudev-hwids
pine64-pinebookpro: fix audio after 5.14 kernel upgrade (MR 2473) ucm2 paths changed after the kernel upgrade [ci:skip-build] already built successfully in CI
2021-08-31 03:09:58 +00:00
linux-postmarketos-rockchip>=5.14
pine64-pinebookpro: add service for setting low power state on boot (MR 2306) This adds a very basic openrc runscript that sets the power state on /dev/nvme0 to level 2, which seems(?) to be the lowest operational power state based on some cursory internet searching (and querying the nvme drives I have, Samsung EVO and Pro) The drive path is hard coded, but could be made configurable later on. I basically wanted to get something in pmaports quickly, since this power stuff is a major source of instability for me and probably others too who add nvme drives to this device.
2021-07-04 00:38:55 +00:00
nvme-cli
pine64-pinebookpro: depend on postmarketos-base>=25-r1 (MR 3791)
2023-01-08 18:20:17 +00:00
postmarketos-base>=25-r1
pine64-pinebookpro: depend on soc-rockchip-rk3399 (MR 4337)
2023-08-18 23:26:05 +00:00
soc-rockchip-rk3399
pine64-pinebookpro: add service for setting low power state on boot (MR 2306) This adds a very basic openrc runscript that sets the power state on /dev/nvme0 to level 2, which seems(?) to be the lowest operational power state based on some cursory internet searching (and querying the nvme drives I have, Samsung EVO and Pro) The drive path is hard coded, but could be made configurable later on. I basically wanted to get something in pmaports quickly, since this power stuff is a major source of instability for me and probably others too who add nvme drives to this device.
2021-07-04 00:38:55 +00:00
u-boot-pinebookpro
pine64-pinebookpro: changes for the 5.13 kernel (MR 2299) * Add the fusb302 module in initfs for the keyboard and touchpad * Add cmdline params for improving stability fw_devlink was switched on by default in kernel 5.13, and is rumored to have issues. The others might improve nvme stability. * Disable wifi powersave * Clean up modules in the deviceinfo
2021-07-02 08:56:54 +00:00
iw
pine64-pinebookpro: add service for setting low power state on boot (MR 2306) This adds a very basic openrc runscript that sets the power state on /dev/nvme0 to level 2, which seems(?) to be the lowest operational power state based on some cursory internet searching (and querying the nvme drives I have, Samsung EVO and Pro) The drive path is hard coded, but could be made configurable later on. I basically wanted to get something in pmaports quickly, since this power stuff is a major source of instability for me and probably others too who add nvme drives to this device.
2021-07-04 00:38:55 +00:00
"
device/pine64-{pinebookpro,rockpro64}: new device (MR 882) [ci:skip-build]
2020-04-07 17:56:30 +00:00
makedepends="devicepkg-dev"
device-pine64-pinebookpro: add elogind subpackage (MR 4202) Move the elogind configuration and post-install call of "loginctl reload" into an extra subpackage with install_if=elogind. Fix for: Executing device-pine64-pinebookpro-16-r0.post-install * service nvme-powersave added to runlevel boot * service sysfsconf added to runlevel default lib/apk/exec/device-pine64-pinebookpro-16-r0.post-install: line 5: loginctl: not found ERROR: device-pine64-pinebookpro-16-r0.post-install: script exited with error 127 Make the post-install scripts more robust while at it, by adding "exit 0" at the end.
2023-06-28 06:27:06 +00:00
subpackages="$pkgname-nonfree-firmware:nonfree_firmware $pkgname-elogind"
install="
$pkgname.post-install
$pkgname.post-upgrade
$pkgname-elogind.post-install
$pkgname-elogind.post-upgrade
"
device/pine64-{pinebookpro,rockpro64}: new device (MR 882) [ci:skip-build]
2020-04-07 17:56:30 +00:00
source="
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
modules-initfs
pine64-pinebookpro: add service for setting low power state on boot (MR 2306) This adds a very basic openrc runscript that sets the power state on /dev/nvme0 to level 2, which seems(?) to be the lowest operational power state based on some cursory internet searching (and querying the nvme drives I have, Samsung EVO and Pro) The drive path is hard coded, but could be made configurable later on. I basically wanted to get something in pmaports quickly, since this power stuff is a major source of instability for me and probably others too who add nvme drives to this device.
2021-07-04 00:38:55 +00:00
nvme-powersave.initd
pine64-pinebookpro: changes for the 5.13 kernel (MR 2299) * Add the fusb302 module in initfs for the keyboard and touchpad * Add cmdline params for improving stability fw_devlink was switched on by default in kernel 5.13, and is rumored to have issues. The others might improve nvme stability. * Disable wifi powersave * Clean up modules in the deviceinfo
2021-07-02 08:56:54 +00:00
wlan-powersave-off.start
device-pine64-pinebookpro: Enable s2idle in elogind. (MR 4194) [ci:skip-build]: already built successfully in CI
2023-06-20 02:56:42 +00:00
enable-s2idle.conf
device/pine64-{pinebookpro,rockpro64}: new device (MR 882) [ci:skip-build]
2020-04-07 17:56:30 +00:00
"
build() {
devicepkg_build $startdir $pkgname
}
package() {
devicepkg_package $startdir $pkgname
pine64-pinebookpro: add service for setting low power state on boot (MR 2306) This adds a very basic openrc runscript that sets the power state on /dev/nvme0 to level 2, which seems(?) to be the lowest operational power state based on some cursory internet searching (and querying the nvme drives I have, Samsung EVO and Pro) The drive path is hard coded, but could be made configurable later on. I basically wanted to get something in pmaports quickly, since this power stuff is a major source of instability for me and probably others too who add nvme drives to this device.
2021-07-04 00:38:55 +00:00
install -D -m755 "$srcdir"/nvme-powersave.initd \
"$pkgdir"/etc/init.d/nvme-powersave
pine64-pinebookpro: changes for the 5.13 kernel (MR 2299) * Add the fusb302 module in initfs for the keyboard and touchpad * Add cmdline params for improving stability fw_devlink was switched on by default in kernel 5.13, and is rumored to have issues. The others might improve nvme stability. * Disable wifi powersave * Clean up modules in the deviceinfo
2021-07-02 08:56:54 +00:00
install -D -m755 "$srcdir"/wlan-powersave-off.start \
"$pkgdir"/etc/local.d/wlan-powersave-off.start
device-pine64-pinebookpro: add elogind subpackage (MR 4202) Move the elogind configuration and post-install call of "loginctl reload" into an extra subpackage with install_if=elogind. Fix for: Executing device-pine64-pinebookpro-16-r0.post-install * service nvme-powersave added to runlevel boot * service sysfsconf added to runlevel default lib/apk/exec/device-pine64-pinebookpro-16-r0.post-install: line 5: loginctl: not found ERROR: device-pine64-pinebookpro-16-r0.post-install: script exited with error 127 Make the post-install scripts more robust while at it, by adding "exit 0" at the end.
2023-06-28 06:27:06 +00:00
}
device-pine64-pinebookpro: Enable s2idle in elogind. (MR 4194) [ci:skip-build]: already built successfully in CI
2023-06-20 02:56:42 +00:00
device-pine64-pinebookpro: add elogind subpackage (MR 4202) Move the elogind configuration and post-install call of "loginctl reload" into an extra subpackage with install_if=elogind. Fix for: Executing device-pine64-pinebookpro-16-r0.post-install * service nvme-powersave added to runlevel boot * service sysfsconf added to runlevel default lib/apk/exec/device-pine64-pinebookpro-16-r0.post-install: line 5: loginctl: not found ERROR: device-pine64-pinebookpro-16-r0.post-install: script exited with error 127 Make the post-install scripts more robust while at it, by adding "exit 0" at the end.
2023-06-28 06:27:06 +00:00
elogind() {
install_if="$pkgname=$pkgver-r$pkgrel elogind"
device-pine64-pinebookpro: Enable s2idle in elogind. (MR 4194) [ci:skip-build]: already built successfully in CI
2023-06-20 02:56:42 +00:00
install -D -m644 "$srcdir"/enable-s2idle.conf \
device-pine64-pinebookpro: add elogind subpackage (MR 4202) Move the elogind configuration and post-install call of "loginctl reload" into an extra subpackage with install_if=elogind. Fix for: Executing device-pine64-pinebookpro-16-r0.post-install * service nvme-powersave added to runlevel boot * service sysfsconf added to runlevel default lib/apk/exec/device-pine64-pinebookpro-16-r0.post-install: line 5: loginctl: not found ERROR: device-pine64-pinebookpro-16-r0.post-install: script exited with error 127 Make the post-install scripts more robust while at it, by adding "exit 0" at the end.
2023-06-28 06:27:06 +00:00
"$subpkgdir"/usr/lib/elogind/sleep.conf.d/enable-s2idle.conf
device/pine64-{pinebookpro,rockpro64}: new device (MR 882) [ci:skip-build]
2020-04-07 17:56:30 +00:00
}
nonfree_firmware() {
pkgdesc="Wifi, Bluetooth and video-out firmware"
pine64-pinebookpro: use linux-firmware packages (MR 4112) The `firmware-pine64-pinebookpro` predates the firmware for this device being available upstream. It is now packaged in two separate packages: linux-firmware-brcm and linux-firmware-rockchip. Install those two linux-firmware packages and drop the custom one. This drop a custom firmware package and also ensure that firmware is kept up to date with the rest of linux-firmware-*. The resulting installation includes all the previously included firmware files and I've confirmed that both sound and wifi work fine (dmesg indicates bluetooth is available too).
2023-05-24 11:01:39 +00:00
depends="linux-firmware-brcm linux-firmware-rockchip"
device/pine64-{pinebookpro,rockpro64}: new device (MR 882) [ci:skip-build]
2020-04-07 17:56:30 +00:00
mkdir "$subpkgdir"
}
pine64-pinebookpro: add service for setting low power state on boot (MR 2306) This adds a very basic openrc runscript that sets the power state on /dev/nvme0 to level 2, which seems(?) to be the lowest operational power state based on some cursory internet searching (and querying the nvme drives I have, Samsung EVO and Pro) The drive path is hard coded, but could be made configurable later on. I basically wanted to get something in pmaports quickly, since this power stuff is a major source of instability for me and probably others too who add nvme drives to this device.
2021-07-04 00:38:55 +00:00
sha512sums="
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
7ebb7e00ae1566fd4c176839c4cd6501f237b577e8db1180aa9934d70101807f8f9b513e529da3f0e96b73d682708b1f51a94430bc90d655f0d7ac059b076a04 deviceinfo
6e3d97855a1f898db46b87ae1eb190d23d841fcb72332fcac4d11cd27c8f7d50eb8fd73007ed0447f106d19ff2e0fc1f34da1baf890e1465135dd692d65df2ba modules-initfs
pine64-pinebookpro: add service for setting low power state on boot (MR 2306) This adds a very basic openrc runscript that sets the power state on /dev/nvme0 to level 2, which seems(?) to be the lowest operational power state based on some cursory internet searching (and querying the nvme drives I have, Samsung EVO and Pro) The drive path is hard coded, but could be made configurable later on. I basically wanted to get something in pmaports quickly, since this power stuff is a major source of instability for me and probably others too who add nvme drives to this device.
2021-07-04 00:38:55 +00:00
2abfa31fa56028339efc6d2b6cb838f310990d7110ac4dd996bc4cfcf90f0a8770e70f28f77f7b6929d110e494bc33731302f16b9717729f991c2732be0731d5 nvme-powersave.initd
pine64-pinebookpro: changes for the 5.13 kernel (MR 2299) * Add the fusb302 module in initfs for the keyboard and touchpad * Add cmdline params for improving stability fw_devlink was switched on by default in kernel 5.13, and is rumored to have issues. The others might improve nvme stability. * Disable wifi powersave * Clean up modules in the deviceinfo
2021-07-02 08:56:54 +00:00
0fd7580e197e409978c219726af627cabe347404ee826e32892b61f3da1775b0fd81f8ed5e9a0f0bfaad87faa434d7a73ddaebf475ed0ad8fdcef6690cd692d3 wlan-powersave-off.start
device-pine64-pinebookpro: Enable s2idle in elogind. (MR 4194) [ci:skip-build]: already built successfully in CI
2023-06-20 02:56:42 +00:00
811af9c79151f41e25916c0f0bb130e82ebfb7d4d5b63413a3fed6700f829c1c017a12e85da230ed2f47a6bd49ed2bf5da19bbc4576ce485a48a2d3808a3a691 enable-s2idle.conf
pine64-pinebookpro: add service for setting low power state on boot (MR 2306) This adds a very basic openrc runscript that sets the power state on /dev/nvme0 to level 2, which seems(?) to be the lowest operational power state based on some cursory internet searching (and querying the nvme drives I have, Samsung EVO and Pro) The drive path is hard coded, but could be made configurable later on. I basically wanted to get something in pmaports quickly, since this power stuff is a major source of instability for me and probably others too who add nvme drives to this device.
2021-07-04 00:38:55 +00:00
"
Reference in a new issue Copy permalink