Building this package aborts in build.postmarketos.org when building for
non-x86_64 architectures, because the "check_hd" program that runs
during the build and already takes a long time without printing any
logs, takes so long in QEMU that it hits the 15 minute timeout. It
writes to a logfile in the process, so attach a tail to it as
workaround.
After fixing that, the build failed because it tried to run a compiler
in package(). Work around it by setting options="!pmb:crossdirect".
[ci:skip-vercheck]
Fixes: https://builds.sr.ht/~postmarketos/job/1863376
Signed-off-by: Oliver Smith <ollieparanoid@postmarketos.org>
Part-of: <https://gitlab.postmarketos.org/postmarketOS/pmaports/-/merge_requests/9390>
libx86emu only exists on x86 and x86_64. Because of this, the
hwinfo APKBUILD has to use conditional dependencies to install
it when it is available. pmbootstrap doesn't have support for
this logic currently, so creating a dummy, empty package for
arches that doesn't have it works.
Signed-off-by: Aster Boese <asterboese@mailbox.org>
Part-of: <https://gitlab.postmarketos.org/postmarketOS/pmaports/-/merge_requests/9160>
The presence of udevadm in both /bin/ and /sbin/ causes usr-merge to assume
a binary conflict and fail. I actually tried fixing this issue upstream quite
a few months ago to fix an unrelated issue I was having with the package, but
it was rejected. Therefore, this can only be handled downstream.
Signed-off-by: Aster Boese <asterboese@mailbox.org>
[ci:skip-vercheck]
Part-of: <https://gitlab.postmarketos.org/postmarketOS/pmaports/-/merge_requests/9160>
This is a bootloader for Open Firmware PowerPC systems that we will use
to replace grub-ieee1275 in device-generic-ppc64le. Due to its use of
RUSTC_BOOTSTRAP, this APKBUILD cannot go to Alpine at the moment, but
once the Rust targets are added upstream, this can be moved to aports.
Part-of: <https://gitlab.postmarketos.org/postmarketOS/pmaports/-/merge_requests/9002>
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>
Replace the dmabuf import patch with the two series that it grow into
during upstreaming, shipping in the next libcamera release. This will:
1. Improve performance for all devices using the GPU-ISP, including
those not able to use dmabuf import.
2. Simplify debugging.
3. Ensure the patches get enough testing before the upstream release.
While on it backport some additional patches:
1. A follow-up patch adding the last required step to allow dmabuf import
for input buffers to work in almost all cases *if* the V4L2 driver
handles custom bytesperline requests for bayer formats.
2. A small logging fix
3. A fix for bad bottom lines of pixels seen on some devices. This is
the only patch with visual impact - and a quite desirable one.
4. A patch to log the used driver for easier debugging.
This leaves us with only two downstream patches, both specific to the
PinePhone (OG).
Finally, add a "py3-$pkgname-pyc:pyc" subpackage in order to stay in
sync with the upstream package.
Part-of: <https://gitlab.postmarketos.org/postmarketOS/pmaports/-/merge_requests/8650>
Fixes the back key on TV remotes not being mapped to escape thus making
it impossible to navigate "back" in applications and menus, and ensures
the virtual keyboard is enabled. Furthermore it now hides the KDE
Connect app and the mouse cursor when not actually used.
The bug referenced in the APKBUILDs is 3 years old and I cannot
reproduce it anymore when cross compiling from x86_64.
This syncs the enabled architectures with Alpine.
[ci:skip-vercheck]: enabling packages for arch
Part-of: <https://gitlab.postmarketos.org/postmarketOS/pmaports/-/merge_requests/7858>
Standardize the use of pkgver=9999$_pkgver, allowing easier upgrades but
also a single expected behaviour for users like nightly-builder.
[ci:skip-vercheck]: some package have the same $pkgver-r$pkgrel
[ci:ignore-count]: this is expected
Part-of: <https://gitlab.postmarketos.org/postmarketOS/pmaports/-/merge_requests/7802>
Oliver Smith