Remove Grub and replace with mainline u-boot & systemd-boot. The two
methods to boot now:
- Hold the RE button to boot off of the SD Card
- With a blank SPI, boot off of eMMC using the power button
SPI needs to be blank as u-boot chainloading is broken
Signed-off-by: Rudraksha Gupta <guptarud@gmail.com>
Part-of: <https://gitlab.postmarketos.org/postmarketOS/pmaports/-/merge_requests/9135>
Unarchives the 'volla-yggdrasil' device, along with its kernel, and renames
the device package to match the ODM name of the device. This name is used by
most projects (with the exception of Ubuntu Touch) for this device.
The kernel is upgraded from v6.1-rc5 to v6.8. The plan was to upgrade it
further, but 6.9-rc1 introduces a bootloop that I don't have the means to
debug at the moment. Thus, reintroduce the kernel at the newest working
version and it will be upgraded in a separate MR once the bootloop is
figured out.
himax_hx83112b is added to the initramfs and enabled in the kernel in
preparation for its enablement in the device tree.
Signed-off-by: Aster Boese <asterboese@mailbox.org>
Part-of: <https://gitlab.postmarketos.org/postmarketOS/pmaports/-/merge_requests/9350>
There is the ocasional or rare case in which this can be useful
independently of [ci:skip-build], like if something is very urgent and
blocked due to something that only affects HW-CI. We already do not
block merging if actual HW fails the tests to avoid reliability
issues, so this is purely for software bugs.
Signed-off-by: Pablo Correa Gómez <pabloyoyoista@postmarketos.org>
Part-of: <https://gitlab.postmarketos.org/postmarketOS/pmaports/-/merge_requests/9348>
Some reasons why I think we want to use resolved by default:
- split DNS support (e.g. for VPNs)
- DNS caching
- roaming (switching between wifi, cell, etc) is handled better since DNS
is tracked per link and the cache is flushed on config changes, so
there are no stale DNS answers when a device switches
- allows users to easily enable dnssec and DoT (even if we aren't
enabling these by deafult right now)
Signed-off-by: Clayton Craft <craftyguy@postmarketos.org>
Part-of: <https://gitlab.postmarketos.org/postmarketOS/pmaports/-/merge_requests/9109>
This logic is "borrowed" from Fedora, and replaces /etc/resolv.conf with
a symlink to the systemd-resolved stub. Fedora does this from an install
script, but that doesn't work for image-based installs since those never
run install scripts on the device, and /etc persists across updates.
I've also seen cases in testing where the symlink was removed by e.g.
accidentally running resolvconf or something similar. So
this runs from a oneshot unit at boot instead, which is ordered before
network-pre.target so NetworkManager doesn't get there first. The old
resolved.post-install script is dropped since the unit covers both cases.
There are some conditions where resolv.conf is **not** replaced:
- when resolv.conf is already a symlink
- when systemd-resolved isn't enabled
- when its stub listener is disabled (via DNSStubListener= in config)
- when systemd isn't running, since resolved isn't either and replacing
resolv.conf would just break dns (e.g. when running the unit's script
by hand)
- when resolv.conf is a bind mount (e.g. in a chroot or container)
This assumes that if a user/sys admin wants to hand-roll their own
resolv.conf, that they either disable the systemd-resolved unit or
disable the stub listener in config if they want to use foreign mode.
The resolved drop-ins are also renamed with a 10- prefix, to match the
numbering ranges UAPI.6 recommends for vendor config in /usr.
Signed-off-by: Clayton Craft <craftyguy@postmarketos.org>
Part-of: <https://gitlab.postmarketos.org/postmarketOS/pmaports/-/merge_requests/9109>
The efivars backend to pstore will not register if the efivarfs is not
available. efivarfs is the only way the pstore can write into EFI
variables. In linux-next, EFI_VARS_PSTORE now depends on EFIVAR_FS, and
we currently have a mismatch in options (EFI_VARS_PSTORE=y andn also
EFIVAR_FS=m), which breaks kconfigcheck on linux-next. To resolve it, we
should build EFIVAR_FS built-in.
Part-of: <https://gitlab.postmarketos.org/postmarketOS/pmaports/-/merge_requests/9343>
Comply with pmOS, which prefers to store hwdb in /etc. openrc works
differently, or at least the packaging in pmOS/Alpine does, so manually
recompile hwdb at package installation time in that case.
Fixes: a99f680468 ("device-blackberry-key2-generic: additional unl0kr fixes")
Signed-off-by: Sicelo A. Mhlongo <absicsz@gmail.com>
Part-of: <https://gitlab.postmarketos.org/postmarketOS/pmaports/-/merge_requests/9335>
The downstreamkernel_* functions assume the presence of a cross GCC and
binutils and should not be used for close-to-mainline kernel packages.
While at it, let's get rid of some unused dependencies and use
postmarketos-installkernel rather than Alpine's.
Part-of: <https://gitlab.postmarketos.org/postmarketOS/pmaports/-/merge_requests/8124>
This kernel version is already EOL at this point, but at the moment
this is the best that we have in state "ready for packaging".
It is still important to get this in to allow creation of packages
for new devices.
New devices:
* Vsmart Active 1 (zangyapro) https://wiki.postmarketos.org/wiki/Vsmart_Active_1_(vsmart-zangyapro)
* Xiaomi Mi Note 3 (jason) https://wiki.postmarketos.org/wiki/Xiaomi_Mi_Note_3_(xiaomi-jason)
New features:
* Speaker Amplifier (TAS2557) driver for a buch of xiaomi-sdm660 devices
* Audio support for jasmine, tulip
* IR blaster for jasmine, tulip
Smaller fixes:
* GPU iommu faults fix (hangs still happen though)
* fix sound card name prefix when using UEFI booting
* sdm660-blackberries shourtcut key fix (is now Ctrl)
* synaptics rmi4 touchscreen reset_gpio support
Packaging:
* conform to new kconfigcheck requirements and add new makedepends
* fix modules installation path to /usr/lib ( #4803 )
Signed-off-by: Alexey Minnekhanov <alexeymin@postmarketos.org>
Part-of: <https://gitlab.postmarketos.org/postmarketOS/pmaports/-/merge_requests/9224>
DEBUG_INFO_DWARF5 conflicts with DEBUG_INFO_BTF on kernel versions older than
5.18. Because debugging failures with DWARF4 would be a waste of time on such
old kernel versions, it is better to just version gate BTF to only support
kernels that can use it with DWARF5.
Signed-off-by: Aster Boese <asterboese@mailbox.org>
Part-of: <https://gitlab.postmarketos.org/postmarketOS/pmaports/-/merge_requests/9038>
Rudraksha Gupta