We now have a bot that reads those lines from APKBUILD files, instead
of using a proprietary gitlab feature. Relevant changes:

* Change @ollieparanoid for @Newbyte as maintainer for GNOME packages
  where Oliver was listed.
* Don't add @craftyguy as Librem5 maintainer, as he dropped it long
  ago
* Remove entries referencing archived ports
* Don't touch jenneron's maintainership. That's a task for another day
* Don't add "balejk" as maintainer. We have tried pinging them, but
  seem to be currently idle
  person is. Help figuring it out would be welcomed.
* Don't add "binarycraft" as maintainer. Last contribution was years
  ago: https://gitlab.com/binarycraft
* Don't add more maintainers to linux-postmarketos-qcom-msm8953, as it
  would have ended up with 7, which might be a bit too much
* Don't add more maintainers to the PinePhone. The current ones seem
  to actually be the most active
* Don't add Danct12 to N900. Sic...

pmbootstrap 3.0.0 uses GPT partition table by default, which breaks booting
on all the devices using the lk2nd bootloader. The current version of lk2nd
supports GPT only for the eMMC, while subpartitions and SD cards must be
partitioned with MBR. GPT support was present in the legacy branch of
lk2nd, but was dropped at some point because of poor code quality.

Fix the regression for now by reverting back to the old msdos (MBR)
partition table. We can revert this again later when lk2nd restores support
for GPT.

Generated with
$ for d in $(grep -R linux-postmarketos-qcom-msm8916 | grep -Eo 'device-[^/]+' | sort -u); do \
  echo -e '\n# lk2nd does not support GPT for subpartitions/SD cards yet\ndeviceinfo_partition_type="msdos"' \
  >> device/*/$d/deviceinfo && pmbootstrap checksum $d && pmbootstrap pkgver_bump $d; done

[ci:ignore-count]

[ci:skip-build]: bug in CI prevents build testing armv7 and aarch64, so
Clayton did the test locally for those archs

Caleb Connolly authored 9 months ago and Oliver Smith committed 9 months ago

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

Nikita Travkin authored 1 year ago and Clayton Craft committed 1 year ago

Now as boot-deploy allows us to generate both boot.img and extlinux.conf
at the same time, enable generating the config for all msm8916 since it
will be used in the future lk2nd release. boot.img is still kept to keep
compatibility with current lk2nd releases and to allow system recovery
with fastboot when required.

[ci:skip-build] already built successfully in CI
[ci:ignore-count]

[ci:ignore-count]

Pablo Correa Gomez authored 1 year ago and Oliver Smith committed 1 year ago

[ci:ignore-count]
[ci:skip-build]: already built successfully in CI

Add rt5033 modules to initfs for the following devices, to unlock FDE with
USB OTG keyboards:

- Samsung Galaxy A3/A5/A7
- Samsung Galaxy E7
- Samsung Galaxy Grand Max

Pablo Correa Gomez authored 1 year ago and Oliver Smith committed 1 year ago

The file is automatically packed by devicepkg-dev utils

Relates #1836

Raymond Hackley authored 2 years ago and Oliver Smith committed 2 years ago

Some devices have 04e8:6860 as their USB ID. Add it to deviceinfo.

[ci:ignore-count]
[ci:skip-build]: already built successfully in CI

Minecrell authored 3 years ago and Dylan Van Assche committed 3 years ago

It seems like at least samsung-a5 needs the same "facility lock"
workaround as samsung-serranove, otherwise ModemManager can not detect
the SIM card correctly. Move it to a subpackage of soc-qcom-msm8916
and apply it to samsung-a3 as well just to be sure.

So far this issue seems limited to Samsung devices, at least bq-paella
is not affected (tested with the same SIM card), so it does not seem
right to apply it unconditionally to all devices.

[ci:skip-build] Already built successfuly on CI in MR

Raymond Hackley authored 3 years ago and Alexey Minnekhanov committed 3 years ago

Fixes: #1422

[ci:ignore-count]

Jakko authored 3 years ago and Oliver Smith committed 3 years ago

Remapping the left key of tm2-touchkey to KEY_MENU.

The KEY_APPSELECT, which is set by the device tree, is not available in
the postmarketOS UIs. In X11 UIs this is due to keycode limitation to
8 bit. In Wayland UIs the keycodes don't have this limitation but xkb
keycodes higher 255 are not processed correctly by several software
packages. It still makes sense to keep KEY_APPSELECT in the device tree
because this is the correct mapping intended by the manufacturers when
running the kernel on Android.

Minecrell authored 3 years ago and Clayton Craft committed 3 years ago

Rule D: Devices with secure boot and venus present in the firmware
        partition need:

  1. GPU firmware (firmware-qcom-adreno-a300)
  2. msm-firmware-loader (for wcnss, modem, venus)
  4. device-specific -wcnss-nv firmware

[ci:ignore-count]
[ci:skip-build] already built successfully in CI

Nikita Travkin authored 3 years ago and Alexey Minnekhanov committed 3 years ago

Right now we have multiple variants of A5 that are only different in
secure-boot keys and as such different firmware blobs.
Use msm-firmware-loader to support all A5 variants with a single device
port. Because of that, drop lte suffix as there are 3g variants as well.