NFS allow the user to mount distant resources locally, and this is
specially great for mobiles devices, with limited disk space. The user
can couple this with FS-Cache, to limit the network impact. Kerberos
bring security to the NFS mounting.
This new category "netmout" make sure the kernels are built to support
this.
Mirror some of the changes to the Pixel 3a:
device-google-sargo: add sensors support (MR 5329)
google-sargo: add gpi to modules-initfs to fix fde (MR 5347)
google-sargo: do not enable HexagonRPCD on every upgrade (MR 5400)
google-sargo: stop HexagonRPCD on suspend (MR 5400)
google-sargo: make necessary userspace changes for kernel v6.10.2
device-google-sargo: remove nonfree_firmware subpkg (MR 6107)
device-google-sargo: Fix hexagonrpcd on systemd (MR 6147)
device-google-sargo: install hexagonrpcd conf to new location (MR 6217)
device/*: explicitly depend on openrc if install scripts call rc-update
Part-of: https://gitlab.postmarketos.org/postmarketOS/pmaports/-/merge_requests/6718
It lets us move the variables in cmdline.txt to
deviceinfo_kernel_cmdline. We can thereafter drop the cmdline.txt file
entirely.
By setting deviceinfo_generate_cmdline_txt we tell boot-deploy to
generate /boot/cmdline.txt from deviceinfo_kernel_cmdline. boot-deploy
can then also add information about partition UUIDs to the cmdline,
which helps postmarketos-initramfs find the correct partitions.
Fixes: https://gitlab.postmarketos.org/postmarketOS/pmaports/-/issues/3716
Part-of: https://gitlab.postmarketos.org/postmarketos/pmaports/-/merge_requests/6630
[ci:skip-build]: already built successfully in CI
It lets us move the variables in cmdline.txt to
deviceinfo_kernel_cmdline. We can thereafter drop the cmdline.txt file
entirely.
By setting deviceinfo_generate_cmdline_txt we tell boot-deploy to
generate /boot/cmdline.txt from deviceinfo_kernel_cmdline. boot-deploy
can then also add information about partition UUIDs to the cmdline,
which helps postmarketos-initramfs find the correct partitions.
Part-of: https://gitlab.postmarketos.org/postmarketos/pmaports/-/merge_requests/6630
It lets us move the variables in cmdline.txt to
deviceinfo_kernel_cmdline. We can thereafter drop the cmdline.txt file
entirely.
By setting deviceinfo_generate_cmdline_txt we tell boot-deploy to
generate /boot/cmdline.txt from deviceinfo_kernel_cmdline. boot-deploy
can then also add information about partition UUIDs to the cmdline,
which helps postmarketos-initramfs find the correct partitions.
Part-of: https://gitlab.postmarketos.org/postmarketos/pmaports/-/merge_requests/6630
It lets us move the variables in cmdline.txt to
deviceinfo_kernel_cmdline. We can thereafter drop the cmdline.txt file
entirely.
By setting deviceinfo_generate_cmdline_txt we tell boot-deploy to
generate /boot/cmdline.txt from deviceinfo_kernel_cmdline. boot-deploy
can then also add information about partition UUIDs to the cmdline,
which helps postmarketos-initramfs find the correct partitions.
Part-of: https://gitlab.postmarketos.org/postmarketos/pmaports/-/merge_requests/6630
It lets us move the variables in cmdline.txt to
deviceinfo_kernel_cmdline. We can thereafter drop the cmdline.txt file
entirely.
By setting deviceinfo_generate_cmdline_txt we tell boot-deploy to
generate /boot/cmdline.txt from deviceinfo_kernel_cmdline. boot-deploy
can then also add information about partition UUIDs to the cmdline,
which helps postmarketos-initramfs find the correct partitions.
Part-of: https://gitlab.postmarketos.org/postmarketos/pmaports/-/merge_requests/6630
It lets us move the variables in cmdline.txt to
deviceinfo_kernel_cmdline. We can thereafter drop the cmdline.txt file
entirely.
By setting deviceinfo_generate_cmdline_txt we tell boot-deploy to
generate /boot/cmdline.txt from deviceinfo_kernel_cmdline. boot-deploy
can then also add information about partition UUIDs to the cmdline,
which helps postmarketos-initramfs find the correct partitions.
Part-of: https://gitlab.postmarketos.org/postmarketos/pmaports/-/merge_requests/6630
Fix the following error that now appears as the systemd-enabled
gnome-keyring package in pmaports will not be built for armhf:
main/postmarketos-ui-xfce4/APKBUILD: package 'gnome-keyring' from _pmb_recommends not found for arch 'armhf'
This happened, because before this patch pmb.helpers.package.get() would
return the pmaports version of the package (!armhf) instead of the one
in the binary packages from alpine (alpine one is available for armhf),
and then later check the arches of the returned package and fail because
it is not enabled for armhf.
With the patch, the binary package from alpine repos is returned as the
pmaports one is ruled out due to not being available for armhf. The
latter arch check is not necessary anymore and gets removed.
Part-of: https://gitlab.postmarketos.org/postmarketOS/pmaports/-/merge_requests/6710
We currently don't build systemd for armhf anymore. Disable all other
packages in the systemd repo too, as these can't be built without the
systemd dependency.
FWIW all of Phosh, Gnome Mobile and Plasma Mobile already have major
packages not building for armhf so they couldn't be used on this arch
anyway.
Once pmb issue 2618 is resolved, we can re-enable systemd for armhf.
Co-authored-by: Oliver Smith <ollieparanoid@postmarketos.org>
Related to !6637Fixes#3783
[ci:skip-build], [ci:skip-vercheck]: changing arch= only
Part-of: https://gitlab.postmarketos.org/postmarketOS/pmaports/-/merge_requests/6710
PostmarketOS now uses ncm instead of rndis, so update script accordingly.
Unfortunately usb networking does not work even after this change when
I test on dream2lte, so this needs further debugging.
Part-of: https://gitlab.postmarketos.org/postmarketOS/pmaports/-/merge_requests/6706
[ci:skip-build]: already built successfully in CI
Notes:
* In general, keybindings are similar to the existing i3 configuration for
the Nokia N900
* Power key and lock switch enable/disable the screen
* The keypad is always lit (dimly) when the screen/touch are active and is
turned off at other times
* The font can be increased/decreased in foot with Ctrl+Up/Down arrow
* The status uses the configuration and feed generator from i3 (i3blocks)
* After two minutes of idle, the screen and touch sensor will be disabled
Part-of: https://gitlab.postmarketos.org/postmarketOS/pmaports/-/merge_requests/6714
[ci:skip-build]: already built successfully in CI
These devices have DRM through the omapdrm kernel driver in mainline.
However, they do not have GPU acceleration, so programs/stacks requiring
GL(ES) will not work. sway and other wlroots-based stacks work well when
WLR_RENDERER=pixman is set.
Part-of: https://gitlab.postmarketos.org/postmarketOS/pmaports/-/merge_requests/6714
Henrik Grimler