[ci:ignore-count]

Required for getting mobile data up, otherwise ModemManager fails to
connect with:

  Status     |                connected: no
             |    connection error name: org.freedesktop.ModemManager1.Error.MobileEquipment.Unknown
             | connection error message: failed to create net link for device: failed to add link for device: Could not allocate link: Failed to add link with mux id 1: Netlink message with transaction 27 failed
[ci:skip-build]: already built successfully in CI

Required for getting mobile data up, otherwise ModemManager fails to
connect with:

  Status     |                connected: no
             |    connection error name: org.freedesktop.ModemManager1.Error.MobileEquipment.Unknown
             | connection error message: failed to create net link for device: failed to add link for device: Could not allocate link: Failed to add link with mux id 1: Netlink message with transaction 27 failed

Rewritten PMIC driver, power key and vibration support are also added in
this upgrade.

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

In many cases, when fw is installed in /lib/firmware, some of it ends up
in the initramfs. In those situations, mkinitfs should run so that the
initramfs gets the latest fw. This will result in mkinitfs possibly
running in cases where it doesn't matter (i.e. device has fw in
/lib/firmware but none is used in the initramfs), but I think the
trade-off is worth it.

This also breaks the triggers= line into multiple lines so that it's
easier to review/maintain. We can't prepend whitespace on these lines
since the apkbuild parser expects dirs to be separated by ":"

See similar patch in pmbootstrap for rationale:
https://gitlab.com/postmarketOS/pmbootstrap/-/commit/27618d5ffdb0b6cbf9471dc01a2ed14e1655ced0

W504 ignore is removed as the rule does not exist in Ruff. But, since it
was ignored anyway, this does not matter.

We use this in pmbootstrap, and it is currently necessary to use Ruff.
Issue about moving Ruff to community:
https://gitlab.alpinelinux.org/alpine/aports/-/issues/15693

fixes #2543

Richard Acayan authored 1 year ago and Alexey Minnekhanov committed 1 year ago

Previously, the modem firmware would be loaded from the modem partition
using this firmware loader. As of the 6.5.4 SDM670 kernel upgrade, the
firmware is installed and loaded from the firmware package. Drop the
dependency on the msm-firmware-loader, which is now unused.

hides some early EFI-related kernel messages from the console

Mohd Bilal authored 1 year ago and Newbyte committed 1 year ago

[ci:skip-build]: Already built successfully in CI.

Newbyte authored 1 year ago and Pablo Correa Gomez committed 1 year ago

We do not want this going forward as we will be changing the wallpaper
on a bi-yearly basis and we do not want to have perform shotgun surgery
every time we do so.

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

Brady Norander authored 1 year ago and Pablo Correa Gomez committed 1 year ago

Krane doesn't have a headphone jack, which caused audio server issues
for me. Add a check to only enable the headphone and headset mic device
on non-Krane boards. Also improve the formatting and remove
ChromeOS-specifc options.

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

Quade Curry authored 1 year ago and Pablo Correa Gomez committed 1 year ago

I would like to maintain this device to keep it in community.

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

Nia Espera authored 1 year ago and Pablo Correa Gomez committed 1 year ago

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

Nia Espera authored 1 year ago and Pablo Correa Gomez committed 1 year ago

Also change source to point to shared sm8350 mainline kernel fork

Clayton Craft authored 1 year ago and Alexey Minnekhanov committed 1 year ago

I was building a branch archive previously, which meant that rebuilding
would fail if someone pushed to the branch upstream (the archive
checksum would change)... so I've reverted back to building from a
specific commit for now.

pkgrel was increased because this commit includes a couple of
audio-related patches that weren't included in the previous packaging of
the 6.7 branch.

[ci:skip-build] Already build-tested on Gitlab CI

Newbyte authored 1 year ago and Pablo Correa Gomez committed 1 year ago

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

mulingLHY authored 1 year ago and Newbyte committed 1 year ago

[ci:skip-build]: Already built successfully in CI.

Alexey Minnekhanov authored 1 year ago and Newbyte committed 1 year ago

Similarly to how it was done for xiaomi-beyllium with varying
display panels, add kernel variant for clover-plus.
Mi Pad 4 Plus is very very similar to regular Mi Pad 4,
but it has different panel and different touchscreen.
Therefore it uses different device tree in kernel - and it
is the only changed line in deviceinfo file.

Signed-off-by: Alexey Minnekhanov <alexeymin@postmarketos.org>

[ci:skip-build]: Already built successfully in CI.

Alexey Minnekhanov authored 1 year ago and Newbyte committed 1 year ago

New devices:
* Xiaomi Mi Pad 4 Plus
  - simpledrm framebuffer
  - touchscreen
  - battery (fuelgauge, charger)
  - radios (modem, Wi-Fi, Bluetooth)

Changes to existing devices:
 * lavender:
   - radios (modem, Wi-Fi, Bluetooth)
   - battery (fuelgauge, charger)
 * tulip:
   - touchscreen
   - fixed vol-down button
   - Bluetooth

Fixes: https://gitlab.com/postmarketOS/pmaports/-/issues/1580
Fixes: https://gitlab.com/postmarketOS/pmaports/-/issues/2501



Signed-off-by: Alexey Minnekhanov <alexeymin@postmarketos.org>

Clayton Craft authored 1 year ago and Newbyte committed 1 year ago

In order to make it work properly, the fcc unlock script from MM should
also be enabled... This info will be added to the device's wiki page for
now since upstream MM discourages distros from enabling these unlock
scripts by default...

fixes https://gitlab.com/postmarketOS/pmaports/-/issues/2489

[ci:skip-build]: Already built successfully in CI.

Gianluca Boiano authored 1 year ago and Newbyte committed 1 year ago

Closes #2531

[ci:skip-build]: Already built successfully in CI.

Add the amdgpu kernel module and its firmware, as it is required for
e.g. the Thinkpad L14 to have any graphical output on boot.

Luca Weiss authored 1 year ago and Alexey Minnekhanov committed 1 year ago

[ci:skip-build] Already built fine on Gitlab CI

Henrik Grimler authored 1 year ago and Newbyte committed 1 year ago

Serial shell on ttySAC2, and kernel upgrades, work well for i9305/m3,
just like for i9300/m0.

[ci:skip-build]: Already built successfully in CI.

The fbdev backend was removed with Weston 10 which has been out for a
good while now. As such, it doesn't matter whether Xwayland works or not
since Weston won't work at all --- the DRM backend, which is what would
get used instead of fbdev with this removed, won't work on downstream
kernels like the one used by this device.

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

The fbdev backend was removed with Weston 10 which has been out for a
good while now. As such, it doesn't matter whether Xwayland works or not
since Weston won't work at all --- the DRM backend, which is what would
get used instead of fbdev with this removed, won't work on downstream
kernels like the one used by this device.

The only relevant backend available for Weston nowadays is the DRM one, so
remove this unnecessary config.

There is no dri-backend.so. I don't know if this ever existed. May have
been a typo where the author meant to type drm-backend.so. The DRM
backend should be the default anyway, so just remove it instead of
fixing what may have been a typo.

The fbdev backend was removed with Weston 10 which has been out for a
good while now. This device should be able to use the DRM backend
anyway given that it uses the A64 SoC which also e.g. the PinePhone
uses.

Additionally, the comment about Xwayland being broken contradicts the
actual configuration file where Xwayland actually is being enabled
(xwayland=true), so this shouldn't be causing any regressions even if it
actually is broken.