In addition to the version upgrade:
1. Drop DTS patch for volume keys. These will be handled via hwdb
2. Drop CONFIG_FW_LOADER_USER_HELPER. It was required by the LED controller
(lp5523) driver until Linux 6.19
3. Restore TWL4030_PWRBUTTON, and make it built-in (in readiness for plymouth)
4. Drop HSI patch. To be replaced with a better quality patch which will be
upstreamed
5. The remainder of changes are from kconfig migrate
Signed-off-By: Sicelo A. Mhlongo <absicsz@gmail.com>
Part-of: <https://gitlab.postmarketos.org/postmarketOS/pmaports/-/merge_requests/8471>
The codeberg tarball fetch was timing out the verify-checksums CI job
(no bytes received after TCP/TLS handshake for 15 minutes). Switch to
Arnav Singh's GitHub mirror of megi's tree, which mirrors the same tag
(orange-pi-6.18-20260105-0049).
The recorded sha512sum changes because GitHub and Gitea (codeberg)
generate tarballs with different bytes for the same git tag.
Also adjust builddir, since GitHub's tarball top-level directory is
named "<repo>-<tag>" (linux-orange-pi-6.18-20260105-0049/) where
codeberg's was just "<repo>" (linux/).
Part-of: <https://gitlab.postmarketos.org/postmarketOS/pmaports/-/merge_requests/8501>
For systemd-logind to allocate VTs automatically when a user switches to them, two
things need to be done. First, logind.conf needs `NAutoVTs=` set to a value, which
in this change is set to the default. Second, getty@.service needs to be symlinked
to autovt@.service, otherwise systemd-logind fails to find the template file.
This change also moves logind.conf to the proper path under `/usr/lib/systemd/`
instead of the sysadmin override path under `/etc/systemd/` and alphanumerically
sorts the sources.
Signed-off-by: Aster Boese <asterboese@mailbox.org>
Part-of: <https://gitlab.postmarketos.org/postmarketOS/pmaports/-/merge_requests/8496>
I have kobo-clarahd and tolino-shine2hd.
kobo-clarahd uses the same board as tolino-shine3, but another
pin-compatible but not software-compatible SoC is installed
tolino-shine2hd uses the same SoC as the tolino-shine3.
So if things are working on both of the devices, it is almost
safe to assume that they will also work on the tolino-shine3.
Based on that assumption add me as a maintainer.
Part-of: <https://gitlab.postmarketos.org/postmarketOS/pmaports/-/merge_requests/8490>
I have kobo-clarahd and tolino-shine2hd.
kobo-clarahd uses the same board as tolino-shine3, but another
pin-compatible but not software-compatible SoC is installed
tolino-shine2hd uses the same SoC as the tolino-shine3.
So if things are working on both of the devices, it is almost
safe to assume that they will also work on the tolino-shine3.
Based on that assumption add me as a maintainer.
Part-of: <https://gitlab.postmarketos.org/postmarketOS/pmaports/-/merge_requests/8490>
This merges system extensions in the initramfs, right before
switch_root, so that the rootfs boot always has the full merged /usr
right from the start. It fixes ordering issues like binfmt starting
before /usr/lib/binfmt.d was merged, and ultimately not working as
expected.
Signed-off-by: Clayton Craft <craftyguy@postmarketos.org>
Part-of: <https://gitlab.postmarketos.org/postmarketOS/pmaports/-/merge_requests/8426>
This will allow folks to easily run mkosi, e.g. for building duranium
images. This makes duranium self-hosting.
There are several key changes in this patch:
- mkosi is added to the duranium developer tools sysext
- user qemu is added to the dev tools sysext (for binfmt+qemu)
- coreutils is added to the main pkg to work around a conflict that Alpine
has with mkosi (see: https://github.com/systemd/mkosi/pull/4283). The
issue is that the busybox symlinks installed in the base duranium image
are not replaced by mkosi when it generates a system extension even if
that sysext pulls in coreutils. coreutils isn't *that* big, so it makes
sense to just have these links correct in the base image.
- duranium dev. tools depends on apk-tools. Wait, what?! mkosi uses
apk to bootstrap a tools tree for building pmOS images. Since we don't
actually want apk to work when run against the duranium rootfs, this
also installs a wrapper that refuses to run apk if it detects that it's
being used "unsafely". To be clear, running apk on duranium's rootfs
won't change /usr or break duranium, but it will: 1) fail, 2) create
confusing state in /etc, /var.
Signed-off-by: Clayton Craft <craftyguy@postmarketos.org>
Part-of: <https://gitlab.postmarketos.org/postmarketOS/pmaports/-/merge_requests/8426>
It doesn't make sense to install apk by default in all flavors of pmOS,
like duranium. To avoid this, apk-tools is moved into a new -apk
subpackage that is pulled in implicitly via install_if. This has the
following benefits:
- postmarketos-duranium can "depend" on !postmarketos-base-apk to
exclude apk-tools
- apk-tools remains a dependency in existing mutable pmOS installs,
so it shouldn't be purged by this change 🤞
- we don't have to update hundreds of APKBUILDs in pmaports that
explicitly depend on `postmarketos-base` to now depend on some other
package that doesn't have apk-tools as an explicit dependency.
After this change, we'll be able to remove some janky cleanup code in
the duranium image build config for uninstalling apk-tools from the base
image, and it will allow us to *add* apk-tools in a system extension
later [1]
Signed-off-by: Clayton Craft <craftyguy@postmarketos.org>
1. https://gitlab.postmarketos.org/postmarketOS/pmaports/-/work_items/4502
Part-of: <https://gitlab.postmarketos.org/postmarketOS/pmaports/-/merge_requests/8426>
I've added support for this device and continue to work on it, so
become maintainer.
Udev rule is just a slight tweak to the one generated by pmbootstrap
when touchscreen details are in deviceinfo, except use the device
name instead of /dev/input/eventX, whose number varies each boot.
Part-of: <https://gitlab.postmarketos.org/postmarketOS/pmaports/-/merge_requests/8470>
Luca Weiss