Commits on Source (66)
-
Add qbootctl as dependency msm-firmware-loader needs it for A/B devices like xiaomi-daisy and xiaomi-tissot. [ci:skip-build]: already built successfully in CI
-
Package auto-update authored
-
We haven't had kernels in main/ for soon three years[1], so no need to bother checking this location. [1]: See commits 47d8f823..8f24fe3a [ci:skip-build]: already built successfully in CI
-
Set partition type to msdos because lk2nd does not support gpt yet. [ci:skip-build]: already built successfully in CI
-
[ci:skip-build]: already built successfully in CI
-
[ci:skip-build]: already built successfully in CI
-
Many parts of the Linux desktop (apps, tools, scripts, etc) all expect xdg-open and friends to be installed. Since these utilities are tiny and (usually) ubiquitous, let's make sure our UIs all depend on them. Signed-off-by:Caleb Connolly <caleb@postmarketos.org>
-
main/postmarketos-base/rootfs-etc-conf.d-zram-init configures zstd as our default ZRAM configuration, but the kconfigcheck only checks for LZ4 at the moment. Because of this some of our kernels don't actually have ZSTD support enabled and end up using the default compression algorithm. For Linux >=4.18 we should enable CONFIG_CRYPTO_ZSTD to enable ZSTD support for ZRAM. In Linux >=6.12 the configuration was changed to CONFIG_ZRAM_BACKEND_ZSTD. This requires manual edits while upgrading, otherwise only LZO support will remain enabled. Checking for >=3.14.0 additionally does not make any sense, because the kconfig check should not be enabled for kernels that cannot satisfy our minimum requirements. Describe this properly in kconfigcheck.toml to ensure kernels are configured correctly. The following kernels are currently missing the correct options: config-htc-flounder.aarch64: CONFIG_CRYPTO_ZSTD should be set (category:zram) config-postmarketos-amlogic.aarch64: CONFIG_CRYPTO_ZSTD should be set (category:zram) config-postmarketos-grate.armv7: CONFIG_CRYPTO_ZSTD should be set (category:zram) config-postmarketos-qcom-msm8974.armv7: CONFIG_CRYPTO_ZSTD should be set (category:zram) config-postmarketos-qcom-sc7280.aarch64: CONFIG_CRYPTO_ZSTD should be set (category:zram) config-postmarketos-qcom-sm6115.aarch64: CONFIG_CRYPTO_ZSTD should be set (category:zram) config-postmarketos-qcom-sm6350.aarch64: CONFIG_CRYPTO_ZSTD should be set (category:zram) config-purism-librem5.aarch64: CONFIG_CRYPTO_ZSTD should be set (category:zram) The following kernels are too old to support CONFIG_CRYPTO_ZSTD: config-samsung-jxelte.aarch64: CONFIG_CRYPTO_ZSTD should be set (category:zram) config-volla-mimameid.aarch64: CONFIG_CRYPTO_ZSTD should be set (category:zram)
-
Linux 3.18.14 has no ZSTD support and is therefore too old to have full support for our default ZRAM configuration. ZRAM will likely still work, but fall back to default compression method. This is not something we can actively test or support, so drop the pmb:kconfigcheck-zram. [ci:skip-vercheck]: no rebuild needed
-
Linux 4.14.186 has no ZSTD support and is therefore too old to have full support for our default ZRAM configuration. ZRAM will likely still work, but fall back to the default compression method. This is not something we can actively test or support, so drop the pmb:kconfigcheck-zram. [ci:skip-vercheck]: no rebuild needed
-
Signed-off-by:Robert Eckelmann <longnoserob@postmarketos.org>
-
Signed-off-by: -
Signed-off-by: -
linux-postmarketos-qcom{msm8974,msm8994,sc7280,sm6115,sm6350}: add CONFIG_CRYPTO_ZSTD/CONFIG_ZRAM_BACKEND_ZSTD (MR 5835) Signed-off-by: -
Signed-off-by: -
[ci:skip-build]: already built successfully in CI
-
Oliver Smith authored[ci:skip-build]: I've built it locally
-
- Update to Linux v6.12.1 - Lots of cleanup and upstreaming, more than 30 commits upstreamed since 6.7 - Various defconfig updates Device changes: - Acer a1-724 gains sound/modem, mount-matrix, simple-framebuffer display - L8910/l9100 (BQ Aquaris X5/M5) gain rgb led - More variants of Lenovo Vibe K5 supported - grandmax gains touchkeys - heatqlte gains backlight - gplus fl8005a gains modem, display, battery - serranove gains hardware-side display flip and brightness control New devices: - Fareastone Smart 506 - Lenovo Yoga Tab 3 10 LTE - Vivo Y21L - ZTE N818s (sapphire)
-
In linux-postmarketos-qcom-msm8916 this is fixed properly thanks to a patch from Jakob Hauser. The cmdline parameter is no longer necessary, and just causes the display to be horizontally flipped again. [ci:skip-build]: already built successfully in CI
-
Oliver Smith authored
Add a workaround so the kernel compile output is not silent (which leads to pmbootstrap aborting the build). This will be fixed once upgrading to linux >= 6.2. Related: pmaports issue 1990 [ci:skip-build]: already built successfully in CI
-
Oliver Smith authored
-
Oliver Smith authored
-
Upgrade to the new v6.12.1 kernel from the vendor. Also disabled unnecessary erratas (they're platform-specific).
-
Package auto-update authored
-
Signed-off-by:Patriot-06 <mbmc172@gmail.com>
-
-
As it's delivered by the distro, it should go into /usr.
-
Package auto-update authored
-
-
-
[ci:skip-build]: already built successfully in CI
-
Package auto-update authored
-
[ci:skip-build]: already built successfully in CI
-
Manual kconfig changes: * EEPROM_AT24 * VIDEO_IMX858 * VIDEO_QCOM_CAMSS * VIDEO_S5KJN1
-
-
-
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]
-
Aster Boese authoredChanges the regex of the initramfs to make sure that it is searching for filesystem type instead of any type (eg partition scheme type).
-
Package auto-update authored
-
bq27xxx_battery has a check for status flags in order to detect changes and report to userspace. However, the cached flags are updated before checking for changes, hence no flag-related events are ever sent. This patch fixes this behavior, and has been sent upstream. [ci:skip-build]: already built successfully in CI
-
For including options to making sure KVM (and others later) is enabled in the kernel. [ci:skip-build]: already built successfully in CI
-
-
Use install "-t" option, avoiding to repeat the file name and allowing to add more than one file per command. Additionally sort the commands alphabetically per path. Exception is the lightdm autologin config file because it does a file renaming. Put this command to the end.
-
The main goal of switching LightDM to slick-greeter is to ease enabling/disabling autologin. With "lightdm-settings" installed, there is an administration/settings GUI "Login Window" available that allows among others to configure autologin. Contrary to its general purpose name, it works on LightDM greeter "slick-greeter" only. [ci:skip-build]: already built successfully in CI
-
The Google Pixel 3a automatically appends console=null to the command line. In the kernel, the preferred console is set to ttynull. Since ttynull is not automatically enabled, a warning is currently emitted: [ 0.909853] Warning: unable to open an initial console. This also causes stdin, stdout, and stderr to be missing from the init process. In the busybox implementation, syslogd creates the /dev/log socket and opens /dev/kmsg. This happens just before daemonizing, which opens /dev/null and aliases stdin, stdout, and stderr to it. After daemonizing and potentially closing the socket, stdin is aliased to the socket to save stack memory. If the program starts without stdin under Linux, the socket gains the constant STDIN_FILENO file descriptor, which is cleared when daemonizing. Syscalls when the 0, 1, 2 file descriptors aren't open: socket(AF_UNIX, SOCK_DGRAM, 0) = 0 openat(AT_FDCWD, "/dev/kmsg", O_WRONLY|O_LARGEFILE) = 1 openat(AT_FDCWD, "/dev/null", O_RDWR|O_LARGEFILE) = 2 Enable the CONFIG_NULL_TTY option and update the configuration to allow the kernel to open stdin, stdout, and stderr for the init and (by inheritance) syslogd processes. It's technically an expert option but isn't enabled by default (and can be enabled in config fragments). Closes #3269 [ci:skip-build]: already built successfully in CI
-
Inspired by the Alpine aports README: https://gitlab.alpinelinux.org/alpine/aports/-/blob/master/README.md?ref_type=heads Co-authored-by:
Clayton Craft <craftyguy@postmarketos.org>
-
Arnav Singh authored -
-
Oliver Smith authored
Fix the following error during "pmbootstrap install": ERROR: unable to select packages: sudo-1.9.16_p1-r1: conflicts: doas-sudo-shim-0.1.1-r1[cmd:sudo=1.9.16_p1-r1] breaks: doas-sudo-shim-0.1.1-r1[!sudo] satisfies: postmarketos-base-38-r0[sudo-virt] postmarketos-base-nofde-38-r0[sudo-virt] doas-sudo-shim-0.1.1-r1: conflicts: sudo-1.9.16_p1-r1[cmd:sudo=0.1.1-r1] satisfies: postmarketos-base-doas-38-r0[doas-sudo-shim] postmarketos-base-38-r0[sudo-virt] postmarketos-base-nofde-38-r0[sudo-virt] How the error gets triggered: * postmarketos-base depends on sudo-virt. During "pmbootstrap install", pmbootstrap has to resolve this to a sudo implementation (sudo, doas, ...). * pmbootstrap does this by looking at the packages that get installed at the same time. Before this patch we did not install doas-sudo-shim directly through _pmb_recommends, only indirectly through a postmarketos-base-doas subpackage that pulls doas-sudo-shim in via install_if. * pmbootstrap cannot look at install_if as it resolves dependencies, so it has to pick one and goes for "sudo". * pmbootstrap tells apk to install a list of packages including "sudo", and because apk also resolves install_if correctly, the solver fails at the conflict between "doas-sudo-shim" and "sudo". (This only fails since apk-tools-static 2.14.6-r0, apparently beforehand apk just installed "doas-sudo-shim" in this scenario.) Teaching pmbootstrap to look at install_if while resolving packages would be one way to fix this. But it would be a lot of effort, not feasible to quickly stop the problem at hand that breaks "pmbootstrap install" for all edge installs. IMHO it is not worth implementing this at all in pmbootstrap, as it is just supposed to do some more or less basic package resolving until apk takes over and does it properly. Put doas-sudo-shim in _pmb_recommends so pmbootstrap knows that this is the sudo implementation we want without looking at install_if. Remove the now obsolete postmarketos-base-doas subpackage. This will lead to doas-sudo-shim getting removed for old installations on upgrade, but it can easily be installed back (doas add doas-sudo-shim). I'll make an edge post about it and put it in the v24.12 release notes. If we don't remove it here, we would need to keep this legacy subpackage around forever and I'd rather avoid that to reduce maintenance effort. Another alternative to this was removing sudo-virt from depends="". But that would lead to sudo getting uninstalled for users upgrading from old releases from before we had doas in pmb_recommends, so I've decided against it. Fixes: pmaports issue 3340 -
Package auto-update authored
-
It's possible that additional sources have been made to an APKBUILD which are unstaged, but if the hunks adding those sources haven't been staged either then it doesn't make sense to fail on this. Use git show to get only the staged hunks for the APKBUILD. Signed-off-by: -
The deviceprofile is now in a tagged sxmo release. The conky issue will be mentioned in wiki for users to manually disable, until upstream allows toggling it.
-
Do not duplicate udev rules that are also shipped by upstream
-
pmos now defaults to droid sans font
-
The bq27200 fuel gauge depends on its battery-backed memory for capacity reporting. If the supply is off for some time, the fuel gauge's last known capacity is reset, after which a capacity value can only be read after a full charge cycle. Thus, most of the time, as used on the Nokia N900, the reported percentage cannot be relied on for making power-off decisions on battery low conditions, e.g. through UPower. However the fuel gauge can very accurately detect and report a low battery condition internally, even if the reported capacity is incorrect, e.g. when it has been reset. The low battery condition is reported by the kernel via capacity_level in sysfs, and also generates uevents. So we can implement safe battery shutdown by requesting the kernel to more regularly polling for status changes, then performing an immediate shutdown when the capacity_level is reported as Low and the device is not charging.
-
As of upower 1.90.5, it is possible to configure upower to not take an action when the battery capacity is reported as critically low. Since the Nokia N900 now monitors its battery capacity using udev scripts, which is more accurate than upower's calculation, enable the new ignore feature for the N900.
-
Package auto-update authored
-
Oliver Smith authored
-
[ci:skip-build]: already built successfully in CI
-
Package auto-update authored
-
Clayton Craft authored
This is a generic kernel for qcom laptops (sc8280xp & x1e), meant to replace the lenovo-21bx kernel for the x13s. - Uses johan_defconfig as base, and includes Minecrell's pmos.config - Adds some extra kconfig for supporting virtualization
-
Clayton Craft authored
-
Clayton Craft authored
[ci:skip-build]: already built successfully in CI
-
[ci:skip-build]: Oliver verified locally that it builds
-
Oliver Smith authored
Fill out makedepends, so pmbootstrap and bpo know that these packages need to be built before building postmarketos-cros-common, because it has subpackages depending on these packages. Without this, bootstrapping v24.12 currently fails: https://builds.sr.ht/~postmarketos/job/1381582 This is intended behavior, abuild works the same way: https://gitlab.alpinelinux.org/alpine/abuild/-/issues/10138 [ci:skip-build]: already built successfully in CI
-
Oliver Smith authored
Split -nofde into a separate package to resolve the cyclic depenency: postmarketos-base -> postmarketos-initramfs -> postmarketos-base-nofde Fixes: issue 3236 [ci:skip-build]: already built successfully in CI
Showing
- .githooks/pre-commit 12 additions, 2 deletions.githooks/pre-commit
- .gitlab-ci.yml 0 additions, 1 deletion.gitlab-ci.yml
- CODEOWNERS 4 additions, 0 deletionsCODEOWNERS
- README.md 5 additions, 1 deletionREADME.md
- cross/busybox-static-aarch64/APKBUILD 2 additions, 2 deletionscross/busybox-static-aarch64/APKBUILD
- cross/busybox-static-armhf/APKBUILD 2 additions, 2 deletionscross/busybox-static-armhf/APKBUILD
- cross/busybox-static-armv7/APKBUILD 2 additions, 2 deletionscross/busybox-static-armv7/APKBUILD
- cross/musl-aarch64/APKBUILD 3 additions, 3 deletionscross/musl-aarch64/APKBUILD
- cross/musl-armhf/APKBUILD 3 additions, 3 deletionscross/musl-armhf/APKBUILD
- cross/musl-armv7/APKBUILD 3 additions, 3 deletionscross/musl-armv7/APKBUILD
- cross/musl-riscv64/APKBUILD 3 additions, 3 deletionscross/musl-riscv64/APKBUILD
- cross/musl-x86/APKBUILD 3 additions, 3 deletionscross/musl-x86/APKBUILD
- cross/musl-x86_64/APKBUILD 3 additions, 3 deletionscross/musl-x86_64/APKBUILD
- device/archived/device-xiaomi-daisy/90-device-xiaomi-daisy.rules 0 additions, 0 deletions...archived/device-xiaomi-daisy/90-device-xiaomi-daisy.rules
- device/archived/device-xiaomi-daisy/APKBUILD 0 additions, 0 deletionsdevice/archived/device-xiaomi-daisy/APKBUILD
- device/archived/device-xiaomi-daisy/deviceinfo 0 additions, 0 deletionsdevice/archived/device-xiaomi-daisy/deviceinfo
- device/archived/device-xiaomi-daisy/modules-initfs 0 additions, 0 deletionsdevice/archived/device-xiaomi-daisy/modules-initfs
- device/archived/device-xiaomi-markw/APKBUILD 0 additions, 0 deletionsdevice/archived/device-xiaomi-markw/APKBUILD
- device/archived/device-xiaomi-markw/deviceinfo 0 additions, 0 deletionsdevice/archived/device-xiaomi-markw/deviceinfo
- device/archived/device-xiaomi-markw/modules-initfs 0 additions, 0 deletionsdevice/archived/device-xiaomi-markw/modules-initfs
File moved
File moved
File moved
File moved
File moved
File moved
File moved