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

58 lines
1.8 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"
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
pkgver=12
pkgrel=0
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: 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"
subpackages="$pkgname-nonfree-firmware:nonfree_firmware"
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="$pkgname.post-install $pkgname.post-upgrade"
device/pine64-{pinebookpro,rockpro64}: new device (MR 882) [ci:skip-build]
2020-04-07 17:56:30 +00:00
source="
deviceinfo
device-pine64-pinebookpro: add udev rule for setting backlight perm (MR 2374) There's a generic udev rule to set group ownership of backlights to 'video', but it only runs on the ADD action, which seems to be too late(?) since the backlight device is never owned by 'video' on boot. This rule will run on CHANGE too, which might be overkill but seems to get the job done. It's now possible to set the backlight brightness on the PBP as a normal user.
2021-07-21 21:37:38 +00:00
70-edp-backlight.rules
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,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 udev rule for setting backlight perm (MR 2374) There's a generic udev rule to set group ownership of backlights to 'video', but it only runs on the ADD action, which seems to be too late(?) since the backlight device is never owned by 'video' on boot. This rule will run on CHANGE too, which might be overkill but seems to get the job done. It's now possible to set the backlight brightness on the PBP as a normal user.
2021-07-21 21:37:38 +00:00
install -D -m644 "$srcdir"/70-edp-backlight.rules \
"$pkgdir"/usr/lib/udev/rules.d/70-edp-backlight.rules
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"
depends="firmware-pine64-pinebookpro"
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="
pine64-pinebookpro: use generated extlinux.conf (MR 3724)
2022-12-11 00:39:55 +00:00
6d6fcb8bbfa2eb0fda691cc646f484ce383ba80bbfd5affde17852913e1f8fe68290fd764f5d7a1cc2f3e9de288a7f4db9ff90dfed66b3a0daf47a0c836e0926 deviceinfo
device-pine64-pinebookpro: add udev rule for setting backlight perm (MR 2374) There's a generic udev rule to set group ownership of backlights to 'video', but it only runs on the ADD action, which seems to be too late(?) since the backlight device is never owned by 'video' on boot. This rule will run on CHANGE too, which might be overkill but seems to get the job done. It's now possible to set the backlight brightness on the PBP as a normal user.
2021-07-21 21:37:38 +00:00
6e9e9ef54ee9aa9491be6dc30451fdcd9038b0efeb959509f48626d97a1696ee81711a46510049557b73269ff48acc85fad6496c65451e2e24908241b7655444 70-edp-backlight.rules
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
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