Alistair Francis authored 2 years ago and Clayton Craft committed 2 years ago

Backport the Purism patch from https://source.puri.sm/Librem5/linux/-/merge_requests/640



"With this patch, older revisions (2.0) should be able to switch between
166MHz and 800MHz as opposed to being stuck to 800MHz all the time, since
that was the only supported frequency in the OPP table."

Signed-off-by: Alistair Francis <alistair@alistair23.me>

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

Minecrell authored 2 years ago and Oliver Smith committed 2 years ago

The WCNSS firwmare used for motorola-harpia seems to have weird issues
that prevent using WiFi properly except for a few limited channels. It
is not clear why this happens, it seems to be some peculiar firmware
difference (perhaps the channels need to be enabled with some
non-standard command).

Since Motorola uses the same signing keys for all their MSM8916
devices, it is possible to use the firmware from other devices instead.
Initial testing shows promising results when using the older WCNSS
firmware from motorola-osprey instead, it does not seem to have this
issue.

It's not clear yet if this has any negative effects. The WCNSS firmware
should not be device-specific, but theoretically it could be (if
Motorola made some weird changes inside it).

For now just package it in firmware-motorola-osprey-wcnss. This package
can be easily installed on harpia devices for testing (using apk add)
and will then take precendence over the default firmware from the
firmware partition (via msm-firmware-loader).

Move firmware-motorola-osprey from testing to community so that the
package is preserved for motorola-harpia users (testing is deleted in
stable branches).

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

Minecrell authored 2 years ago and Oliver Smith committed 2 years ago

motorola-osprey can generally use the firmware from motorola-harpia
(which is a bit newer). However, the WCNSS_qcom_wlan_nv.bin is usually
device specific (it contains some kind of calibration values for
WiFi/BT).

The file packaged in firmware-motorola-osprey-wcnss-nv is identical to
the file in firmware-motorola-harpia-wcnss-nv. However, It looks a bit
like this might be a mistake in the source repository
(https://github.com/pmsourcedump/firmware-motorola-osprey). The
wlan/prima folder there is completely identical to the one used for
motorola-harpia, but the stock ROM and LineageOS use different files.

Fix this by packaging the file from TheMuppets. Also modernize the
firmware-motorola-osprey package by applying pil-squasher to the
venus/video firmware.

Minecrell authored 2 years ago and Oliver Smith committed 2 years ago

This reverts parts of commit 9c8a189e
("motorola-osprey: use firmware from harpia (MR 2613)").

Minecrell authored 2 years ago and Oliver Smith committed 2 years ago

motorola-osprey has a very clunky name at the moment "Motorola Moto G
3rd gen. (2015)". The device was mostly just called "Motorola Moto G"
by Motorola, so it is hard to choose a fitting (but unique) name.

In the postmarketOS wiki it is called "Motorola Moto G 2015" so let's
just drop the "3rd gen." in the pmOS device package as well.

Also make the deviceinfo consistent with harpia while at it.

Anton Bambura authored 2 years ago and Oliver Smith committed 2 years ago

cros-ec-sensorhub is blocked because of wrong accelerometer mount matrix

Kabir Akzaman authored 2 years ago and Clayton Craft committed 2 years ago

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

Elagost authored 2 years ago and Clayton Craft committed 2 years ago

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

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

Anjan Momi authored 2 years ago and Oliver Smith committed 2 years ago

Users can switch to pulseaudio with:
  doas apk add sxmo-audio-common-pulse

We can make the poco f1 device APKBUILD depend on
sxmo-common-audio-pulse. This allows you to install pulseaudio on Sxmo
which was the reason Joel said the poco f1 was having issues with call
audio: https://gitlab.com/postmarketOS/pmaports/-/issues/1821



After installing pulseaudio with this patch, the other side still
cannot hear me. I am posting this work so that others can just run
pulseaudio on sxmo and find out what's causing this bug.

Note by ollieparanoid: while it doesn't fix the bug completely, it seems
it's required to make calling work again, something we definitively want
to have in v22.12 so I'm merging this now. Also the sxmo-utils patch was
merged to sxmo-utils upstream, but isn't in alpine yet. Adding this
package (previous patch) temporarily makes sense.

Co-developed-by: Oliver Smith <ollieparanoid@postmarketos.org>
[ci:skip-vercheck]: pkg forked from alpine has pkgrel > 0
[ci:skip-build]: already built successfully in CI

Anjan Momi authored 2 years ago and Oliver Smith committed 2 years ago

This package is just forked from alpine upstream and patched to support
pulseaudio. This patch should be upstreamed to sxmo but posting here so
that others can help me figure out why audio calls with poco f1 and Sxmo
are broken:

https://gitlab.com/postmarketOS/pmaports/-/issues/1821

Gianluca Boiano authored 2 years ago and Newbyte committed 2 years ago

Signed-off-by: Gianluca Boiano <morf3089@gmail.com>

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

Gianluca Boiano authored 2 years ago and Newbyte committed 2 years ago

Signed-off-by: Gianluca Boiano <morf3089@gmail.com>

Jan Jasper de Kroon authored 2 years ago and Newbyte committed 2 years ago

Schedutil is a CPU scheduler that is designed to be more efficient than other schedulers, such as the conservative scheduler, in terms of energy consumption.
This is because schedutil uses information about the utilization of individual CPU cores to make more intelligent decisions about when and how to scale the frequency of the CPU.
This can help to reduce the overall power consumption of the device, which can be particularly beneficial for battery-powered devices.
Additionally, schedutil can also help to improve the overall performance of the device by ensuring that the CPU is able to operate at its maximum frequency when needed.

In my personal testing I haven't seen any noticable impact on power consumption, while the performance does certainly noticeably increase
Note: This is only a change in the aarch64 configuration as the armv7 configuration already used the schedutil scheduler as default.

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

Raffaele Tranquillini authored 2 years ago and Newbyte committed 2 years ago

This adds initial support to CutiePi tablet, with basic peripherals, sound, touchscreen, and wireless support.

Signed-off-by: Raffaele Tranquillini <raffaele.tranquillini@gmail.com>

Add peripheral overlays

Signed-off-by: Raffaele Tranquillini <raffaele.tranquillini@gmail.com>

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

Jan Jasper de Kroon authored 2 years ago and Newbyte committed 2 years ago

device/community/linux-pine64-pinephonepro: Switch to CONFIG_CPU_FREQ_DEFAULT_GOV_SCHEDUTIL (MR 3719)

Schedutil is a CPU scheduler that is designed to be more efficient than other schedulers, such as the conservative scheduler, in terms of energy consumption.
This is because schedutil uses information about the utilization of individual CPU cores to make more intelligent decisions about when and how to scale the frequency of the CPU.
This can help to reduce the overall power consumption of the device, which can be particularly beneficial for battery-powered devices.
Additionally, schedutil can also help to improve the overall performance of the device by ensuring that the CPU is able to operate at its maximum frequency when needed.

In my personal testing I haven't seen any noticable impact on power consumption, while the performance does certainly noticeably increase

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

Vincent Knecht authored 2 years ago and Newbyte committed 2 years ago

Use msm8916 kernel package instead of linux-postmarketos-qcom-msm8939
Also remove rmi_core from deviceinfo_modules_initfs
since it's automatically pulled by rmi_i2c

Luca Weiss authored 2 years ago and Clayton Craft committed 2 years ago

* Enable flash/torch LED (CONFIG_LEDS_QCOM_FLASH)
* Fix USB init when not plugged in during bootloader stage

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

Oliver Smith authored 2 years ago and Clayton Craft committed 2 years ago

Fix for:
  missing depend(s): so:libtiff.so.5

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

Most of the config diff is from rebasing the kconfig in pmaports with
mainline + purism changes

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

Joel Selvaraj authored 2 years ago and Oliver Smith committed 2 years ago

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

Fix for:
  missing depend(s): so:libcamera.so.0.0.1

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

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

Mas Ahmad Muhammad authored 2 years ago and Newbyte committed 2 years ago

Signed-off-by: Mas Ahmad Muhammad <(m.charly81@gmail.com)>

Mas Ahmad Muhammad authored 2 years ago and Newbyte committed 2 years ago

Signed-off-by: Mas Ahmad Muhammad <(m.charly81@gmail.com)>

Lux Aliaga authored 2 years ago and Newbyte committed 2 years ago

This is a version bump for the sm6125 mainline kernel fork.

Changes:
* Added UFS nodes to the sm6125 platform
* Enabled UFS nodes for xiaomi-laurel
* Enabled configs required for UFS support (Notoriously
CONFIG_PHY_QCOM_QMP)
* Filled in EXTRAVERSION for kernel fork
* Added SMD RPM regulators for xiaomi-laurel

Signed-off-by: Lux Aliaga <they@mint.lgbt>

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

Lux Aliaga authored 2 years ago and Newbyte committed 2 years ago

This commit adds sparse flashing and rootfs sector size to deviceinfo

Signed-off-by: Lux Aliaga <they@mint.lgbt>

Jan Jasper de Kroon authored 2 years ago and Oliver Smith committed 2 years ago

Fix included in this build:
- Patch which sets GPIO pin for stk3311 as input
- ppp: don't reset 'display state of charge' (dsoc) to 0 on vbat low interrupt

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

Anton Bambura authored 2 years ago and Oliver Smith committed 2 years ago

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

David Wronek authored 2 years ago and Clayton Craft committed 2 years ago

Add support for the Xiaomi POCO X3 NFC.

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