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

83 lines
3 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>
pkgname=device-pine64-pinebookpro
pkgdesc="PINE64 Pinebook Pro"
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
pkgver=7
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
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="
alsa-ucm-conf
linux-postmarketos-rockchip
mesa-dri-gallium
nvme-cli
postmarketos-base
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
extlinux.conf
device-pine64-pinebookpro: trackpad and audio fixes (MR 1303) This adds a hwdb override for the trackpad that fixes the reported size, this fixes the acceleration profile and palm detection in libinput. Pulse now follows alsa paths for ucm files so the path for the rk3399 ucm has been updated to match.
2020-06-13 14:16:59 +00:00
10-pinebookpro.hwdb
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
device/pine64-{pinebookpro,rockpro64}: new device (MR 882) [ci:skip-build]
2020-04-07 17:56:30 +00:00
mem_sleep.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
nvme-powersave.initd
device/pine64-{pinebookpro,rockpro64}: new device (MR 882) [ci:skip-build]
2020-04-07 17:56:30 +00:00
ucm/rockchip,es8316-codec.conf
ucm/HiFi
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
install -D -m644 "$srcdir"/extlinux.conf \
"$pkgdir"/boot/extlinux/extlinux.conf
# Keyboard mapping
device-pine64-pinebookpro: trackpad and audio fixes (MR 1303) This adds a hwdb override for the trackpad that fixes the reported size, this fixes the acceleration profile and palm detection in libinput. Pulse now follows alsa paths for ucm files so the path for the rk3399 ucm has been updated to match.
2020-06-13 14:16:59 +00:00
install -D -m644 "$srcdir"/10-pinebookpro.hwdb \
"$pkgdir"/etc/udev/hwdb.d/10-pinebookpro.hwdb
device/pine64-{pinebookpro,rockpro64}: new device (MR 882) [ci:skip-build]
2020-04-07 17:56:30 +00:00
# Sleep workaround
install -D -m644 "$srcdir"/mem_sleep.conf \
"$pkgdir"/etc/sysfs.d/mem_sleep.conf
# Alsa usecase manager config
install -D -m644 "$srcdir"/rockchip,es8316-codec.conf \
device-pine64-pinebookpro: trackpad and audio fixes (MR 1303) This adds a hwdb override for the trackpad that fixes the reported size, this fixes the acceleration profile and palm detection in libinput. Pulse now follows alsa paths for ucm files so the path for the rk3399 ucm has been updated to match.
2020-06-13 14:16:59 +00:00
"$pkgdir"/usr/share/alsa/ucm2/rockchip_es8316/rockchip,es8316-codec.conf
device/pine64-{pinebookpro,rockpro64}: new device (MR 882) [ci:skip-build]
2020-04-07 17:56:30 +00:00
install -D -m644 "$srcdir"/HiFi \
device-pine64-pinebookpro: trackpad and audio fixes (MR 1303) This adds a hwdb override for the trackpad that fixes the reported size, this fixes the acceleration profile and palm detection in libinput. Pulse now follows alsa paths for ucm files so the path for the rk3399 ucm has been updated to match.
2020-06-13 14:16:59 +00:00
"$pkgdir"/usr/share/alsa/ucm2/rockchip_es8316/HiFi
device/pine64-{pinebookpro,rockpro64}: new device (MR 882) [ci:skip-build]
2020-04-07 17:56:30 +00:00
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="
device-pine64-pinebookpro: remove initfs modules that are builtin (MR 2373) These drivers are built into the kernel used by this device, and are not LKMs. [ci:skip-build] already built successfully in CI
2021-07-21 18:01:10 +00:00
541f572b2816f11e95c9793ccc9a9ea33c0fceb3f970bea3560d2dfa61b1e45c6513c048cecf1f96e46c3d094f66830e560c2e5fb747a5dcb69e45ff2d970644 deviceinfo
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
244a321cbc885d7cb90cdc2b905b39efdeaa9d77aa33208aa6b699059a955e5c15247e4dfcd762fd34ece98d686c7da5ffa84acb38044446079f13c193955865 extlinux.conf
device-pine64-pinebookpro: trackpad and audio fixes (MR 1303) This adds a hwdb override for the trackpad that fixes the reported size, this fixes the acceleration profile and palm detection in libinput. Pulse now follows alsa paths for ucm files so the path for the rk3399 ucm has been updated to match.
2020-06-13 14:16:59 +00:00
d3988fe83c54228d743f4a8c190e9530404a436a7fbc0b004bf20d3986b502d864717d8cc9c76812e599266bf84cb08f9a86e1bfd220875799c5a022aea588ec 10-pinebookpro.hwdb
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
device/pine64-{pinebookpro,rockpro64}: new device (MR 882) [ci:skip-build]
2020-04-07 17:56:30 +00:00
bcae155e24a151d3c098833680b83b6004a329962f115480d560ebe19257eab87286b8a4c194e456c067ca54fb53e59a5a16b022cea13c11135b0855145db563 mem_sleep.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
2abfa31fa56028339efc6d2b6cb838f310990d7110ac4dd996bc4cfcf90f0a8770e70f28f77f7b6929d110e494bc33731302f16b9717729f991c2732be0731d5 nvme-powersave.initd
device/pine64-{pinebookpro,rockpro64}: new device (MR 882) [ci:skip-build]
2020-04-07 17:56:30 +00:00
846384cab3e9581a03007cf4f39f8538315e804d1573903dd223d22d5ca0b6f260e348467aead5124689288fb7d2ec22c1e9aba8e89683efdbd33ddfe10de852 rockchip,es8316-codec.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
558f08b56425e0ceeea8d4815eeb862a2b801ba1b26b4dc28f4d0ec991ed9dfef14113172a224191eb2de5d0b57a741e4c48f1307bda2a69595944bd58731be1 HiFi
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