The kernel searches for installkernel in /sbin/. Since postmarketOS
is usr-merged, that would be /usr/sbin/. The installkernel binary
was moved to /usr/bin/ instead, which is the wrong path due to
postmarketOS not being bin-merged.
Signed-off-by: Aster Boese <asterboese@mailbox.org>
Part-of: <https://gitlab.postmarketos.org/postmarketOS/pmaports/-/merge_requests/9012>
Despite the name, this does pull the correct polkit on systemd, as the
systemd/polkit package provides polkit-elogind=9999$_pkgver-r$pkgrel,
which apk will pick, while on OpenRC apk will happily pick
polkit-elogind from alpine repos (pulling polkit that builds against
elogind)
Signed-off-by: Ferass El Hafidi <funderscore@postmarketos.org>
Part-of: <https://gitlab.postmarketos.org/postmarketOS/pmaports/-/merge_requests/8890>
Reorders the keys to match newapkbuild and fixed
the provider, since the current logic made it
always be considered a lower provider priority
than the Alpine installkernel. Also moved the
location of the installed binary to not need
to replace Alpine's installkernel.
Signed-off-by: Aster Boese <asterboese@mailbox.org>
Part-of: <https://gitlab.postmarketos.org/postmarketOS/pmaports/-/merge_requests/8982>
In the most recent xkeyboard-config, the layout changed from
us/pc/key2 to blackberry-key2/us
(layout/model/variant) (model/layout)
The udev hwdb is for unl0kr to properly recognize the keyboard,
recommended by sicelo.
Signed-off-by: Paul Sajna <sajattack@postmarketos.org>
Part-of: <https://gitlab.postmarketos.org/postmarketOS/pmaports/-/merge_requests/8969>
compat-sysv-interfaces is meant for systems that
already have technical debt from switching from
sysv. postmarketOS does not have this, so this
is not needed.
All this option does is enable runlevels 0-6
and install legacy.conf, which also doesn't
work with our packaging because it installs
symlinks who's target only exists in
subpackages.
Signed-off-by: Aster Boese <asterboese@mailbox.org>
Part-of: <https://gitlab.postmarketos.org/postmarketOS/pmaports/-/merge_requests/8996>
As discussed with Casey at the FOSDEM hackathon, we want to integrate
linux-next with the same infra we use for linux-postmarketos-mainline
and the other generic kernels and move maintainership to the generic
kernel team.
Part-of: <https://gitlab.postmarketos.org/postmarketOS/pmaports/-/merge_requests/7937>
The current systemd user namespaces model
almost works with confidentiality, but a single
check for kprobes is used, which confidentiality
disables, so user namespaces fail. For now,
just downgrade lockdown to integrity until this
is sorted out in systemd.
Signed-off-by: Aster Boese <asterboese@mailbox.org>
Part-of: <https://gitlab.postmarketos.org/postmarketOS/pmaports/-/merge_requests/8988>
It's far from perfect but better than the default. Most importantly it
gives users of the OP6 - one of the most popular devices - an impression of
where libcamera development is heading - and an incentive to help/play
around with tuning.
Part-of: <https://gitlab.postmarketos.org/postmarketOS/pmaports/-/merge_requests/8992>
See
https://gitlab.freedesktop.org/camera/libcamera/-/releases/v0.7.2
The release notably includes fixes that allow us to start shipping color
correction matrices in tuning files. This commit includes the current
tuning iterations for the imx363 (used e.g. as Pixel 3a rear camera) and
the s5kjn1 (used on e.g. as FairPhone 5 front camera). The later is also
used for the other correspondig cameras on the mentioned devices, as
they improve the quality over the default. This is of course planed to
change in the future.
The GPU-ISP also received major performance improvements, in particular
if the dmabuf direct import path can be used. If that's not the case
some INFO logs are printed, giving hints what needs to be improved in
the V4L2 or GPU drivers.
Finally we can drop all previously backported patches, only keeping two
PinePhone (OG) specific ones around for now. These should probably be
dropped in future releases, giving the poor performance and limited GPU
capabilities (GLES 2.0 only) on that device.
Part-of: <https://gitlab.postmarketos.org/postmarketOS/pmaports/-/merge_requests/8991>
Enables lockdown by default in the hardening category, but locks hardcoding
enabling confidentiality behind the lockdown category, which kernels can
opt-into where it makes sense.
Signed-off-by: Aster Boese <asterboese@mailbox.org>
Part-of: <https://gitlab.postmarketos.org/postmarketOS/pmaports/-/merge_requests/7369>
_defconfig="defconfig" is the default logic in pmbootstrap, and thus should not be
duplicated in kernel packages. The only use-case for _defconfig is for when the
defconfig differs from what is automatically selected.
linux-next is not modified because it still uses the old kconfig fragments logic and
would break with this change.
Signed-off-by: Aster Boese <asterboese@mailbox.org>
Part-of: <https://gitlab.postmarketos.org/postmarketOS/pmaports/-/merge_requests/8978>
Pulling this in results in a bunch of modem related stuff that isn't
applicable to all Qualcomm devices.
Signed-off-by: Casey Connolly <kcxt@postmarketos.org>
Co-Authored-by: Victoria Brekenfeld <postmarketos@drakulix.de>
Part-of: <https://gitlab.postmarketos.org/postmarketOS/pmaports/-/merge_requests/8980>
_pmb_default is only for changing the default provider from
the package with the highest provider_priority. This package
is using it with the providers that already have the highest
priority, making _pmb_default a no-op. Thus, removing this
is a basic logic cleanup.
Signed-off-by: Aster Boese <asterboese@mailbox.org>
Part-of: <https://gitlab.postmarketos.org/postmarketOS/pmaports/-/merge_requests/8949>
It appears to default to y with our current config requirements from
Linux 7.2 onwards, and that in turn breaks kconfigcheck because it will
set CRYPTO_CAMELLIA=y, etc. If we require it to be built as a module,
our kconfig checks will pass again.
Part-of: <https://gitlab.postmarketos.org/postmarketOS/pmaports/-/merge_requests/8929>
