- Mar 04, 2025
-
-
Pablo Correa Gomez authored
Fixes 85f9a49a
-
- Jan 31, 2025
-
-
Add a note with the reason for archiving and a suggestion to use the generic port (qcom-msm8953), remove maintainers. These individual ports was replaced (MR 5800) by the generic one (qcom-msm8953) [ci:ignore-count] [ci:skip-vercheck]
-
- Jan 07, 2025
-
-
Luca Weiss authored
Like quite a few other values being set to false, this one has a default of false so can be safely removed.
-
This is the port for the Librem 5 devkit, I still have one but haven't booted it in years and it's unlikely anyone else is using this (since this port is super outdated and almost certainly not functional as-is). Let's archive it so that it doesn't cause any confusion. [ci:skip-vercheck] [ci:skip-build]: we don't actually want to build test this thing
-
- Jan 06, 2025
-
-
there is available qcom-msm8953 which is working with latest lk2nd fine on kuntao, but after flashing by building with device-lenovo-kuntao, it is resulting rebooting the system continuously with latest lk2nd, so imo it should be archived
-
- Dec 27, 2024
-
-
[ci:skip-build]
-
- Nov 27, 2024
-
-
Replace individual msm8953 xiaomi packages with generic msm8953 package. Move device-xaiomi-daisy-fake-goodix package to the generic device package. [ci:ignore-count] [ci:skip-vercheck]
-
- Nov 15, 2024
-
-
[ci:skip-build]: already built successfully in CI
-
- Nov 12, 2024
-
-
[ci:skip-build]: already built successfully in CI
-
- Nov 06, 2024
-
-
Clayton Craft authored
I replaced "console=null" with "quiet loglevel=2", based on the findings in #2989 fixes #3269 [ci:ignore-count] [ci:skip-build]: already built successfully in CI
-
- Oct 31, 2024
-
-
device/*/*: enable deviceinfo_create_initfs_extra instead of depending on initramfs-minimal (MR 5636) Make use of the new multi-stage initramfs rather than the minimal variant, and inform mkinitfs that the initramfs-extra archive should be created to save space. Signed-off-by:
Caleb Connolly <caleb@postmarketos.org> [ci:ignore-count]
-
- Oct 19, 2024
-
-
- Jul 07, 2024
-
-
... and install the firmware package using _pmb_recommends instead. Applied to both downstream and mainline ports. [ci:skip-build]: already built successfully in CI
-
- Jun 29, 2024
-
-
Resolves this harmless, but annoying error on mainline: * Enabling wlan driver ... /lib/rc/sh/openrc-run.sh: line 14: can't create /sys/devices/platform/sd8x-rfkill/pwr_ctrl: nonexistent directory * ERROR: sd8x-wlan failed to start [ci:skip-build]: already built successfully in CI
-
-
- Jun 23, 2024
-
-
This cmdline argument is now a no-op. Drop it everywhere and add a new CI check to enforce this. Adjust the deprecated "minimal" initramfs variant to use pmos.debug-shell to enable logging instead. It doesn't /support/ dropping to a shell, so the variable takes on a different meaning. But that's ok since it's at least more consistent. [ci:ignore-count] [ci:skip-vercheck] Signed-off-by:
Caleb Connolly <caleb@postmarketos.org> Tweaked-by:
Oliver Smith <ollieparanoid@postmarketos.org> [ci:skip-build]: kernel builds are very likely to go through now
-
- Jun 18, 2024
- May 15, 2024
-
-
Unmaintained is a name which on multiple occasions have seen lead to confusion with people having the impression that unmaintained is for all unmaintained devices, which is not how we're really using it. Many devices in testing do not actually have a maintainer, yet there has been no push to move these out of there and into unmaintained. I think this is a result of that unmaintained was introduced not to keep unmaintained ports but rather a place to store ports that have a better replacement but where the inferior one still holds some sort of value, such as for debugging purposes. These ports also are not necessarily entirely unmaintained and see more fixes than many ports in testing. While one approach to solving this problem could be to simply moving all unmaintained ports to unmaintained, I think this comes with some problems: It would require an initial effort to figure out which ports are indeed unmaintained and which just don't have a maintained noted in the package, and given how many ports there are in testing this would be a big endeavour. It would also require continuous work on moving ports into unmaintained as the maintainers go silent if we are to keep testing and unmaintained's state consistent with reality. Additionally, just because a port doesn't have a maintainer on paper doens't mean that there aren't people who aren't willing to fix it up if there are issues that arise. As such, I think the way to go is renaming unmaintained to better reflect the original intent. Thanks to Luca Weiss for suggesting "archive", and to Arnav Singh for suggesting that "archived" would match the other category names better.
-