VDavid003 authored 4 years ago and Oliver Smith committed 4 years ago

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

Oliver Smith authored 4 years ago and Alexey Minnekhanov committed 4 years ago

When using '[ci:skip-build]' without any changed packages, do not
attempt to run "pmbootstrap checksum" without any package arguments.
This may happen, because CI in MRs runs across all patches in the MR,
but CI on branches (master, v20.05) only run on the last commit.

Prevents CI failures like this one:
https://gitlab.com/postmarketOS/pmaports/-/commit/9a48b41a2362ba0dd2b0901cae966011b37d1856

Flashing linux-postmarketos-exynos4 to the i9100 requires pmbootstrap MR
1986.

[ci:skip-vercheck]: linux-samsung-i9300: 3.0.101-r1 instead of -r0 is
not a mistake, the linting error fixes are in a separate commit with
their own pkgrel bump. I decided to leave that in its own commit instead
of squashing together with the other commit (as we usually do), because
the linting fixes are quite a lot and it makes the log more readable.
[ci:skip-build]: already built successfully in CI

Thiago Foganholi authored 4 years ago and Oliver Smith committed 4 years ago

The existing device package and its dependencies are for i9305, but
renaming them to i9300 makes more sense, as the i9300 is the base
version (SIII) and the i9305 (SIII LTE) is the improved version.

Thiago Foganholi authored 4 years ago and Oliver Smith committed 4 years ago

With a new mainline kernel package available for this device, add a new
package dependency and allow the user to choose downstream or mainline
kernel.

Thiago Foganholi authored 4 years ago and Oliver Smith committed 4 years ago

The devices supported by this package are Galaxy S3 (GT-I9300, GT-I9305,
SHV-E210K/L/S) and the Galaxy Note 2 (GT-N7100, GT-N7105) - a family of
boards also known by the codename "Midas" - and the Galaxy S2 (GT-I9100)

From this list, only the i9100 doesn't support the bootimg method.
Because of this, this kernel package is using the isorec method for all
the devices on the list. Additionally, for the midas devices, there is
no problem with this because the boot.img file is, in fact, a copy of
the kernel+initramfs on the pmos boot partition and what the isorec
initramfs does is actually to load the initramfs on that partition
directly (at least on my understanding).

Luca Weiss authored 4 years ago and Oliver Smith committed 4 years ago

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

Bart Ribbers authored 4 years ago and Oliver Smith committed 4 years ago

Co-Authored-By: Oliver Smith <ollieparanoid@postmarketos.org>

This reverts commit c3e87a47. It has
been merged in Alpine, no need for our fork.

Currently phosh is broken in postmarketOS edge. Fork wlroots from Alpine
and revert the new consistency check that results in the breakage. I've
submitted the same to Alpine, but let's get it in pmOS now so it is
fixed ASAP.

Alpine MR: https://gitlab.alpinelinux.org/alpine/aports/-/merge_requests/14522
[ci:skip-vercheck]: new package added with -r1 on purpose

Bart Ribbers authored 4 years ago and Oliver Smith committed 4 years ago

There have been support questions about this from users
https://www.reddit.com/r/postmarketOS/comments/jqbqu2/mounting_ecryptfs_encrypted_folder/

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

Luca Weiss authored 4 years ago and Bart Ribbers committed 4 years ago

These haven't been used since converting the APKBUILDs to use
devicepkg-dev, so remove them.

[ci:skip-build]
[ci:ignore-count]
[ci:skip-vercheck]

Luca Weiss authored 4 years ago and Bart Ribbers committed 4 years ago

[ci:skip-build]
[ci:ignore-count]
[ci:skip-vercheck]

        - Upgrade librem5-base config
        - add goodix touch input and edx touchscreen drivers to
          deviceinfo/initramfs

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

This enabled the rfkill service, part of util-linux, that saves/restores
radio device state on shutdown/boot.

fixed #836

Pedro Moreno authored 4 years ago and Oliver Smith committed 4 years ago

Removed 2 actions cause future suspends to trigger a kernel bug that
ends up spamming the kernel log with "ehci-platform 1c1b000.usb: port 1
resume error -110" and eventually makes the device not respond to any
input or hang in shutdown/reboot.

Workaround for issue: #848
Co-Authored-By: Oliver Smith <ollieparanoid@postmarketos.org>

Martijn Braam authored 4 years ago and Oliver Smith committed 4 years ago

Since the installer leaves the partition in a state where the initramfs
needs to resize it. But without the force parameter the postmarketOS
initramfs won't touch the partitions

Luca Weiss authored 4 years ago and Oliver Smith committed 4 years ago

Mostly the GCC10 yylloc failure was seen but several others have been
observed:

* wireguard script was silently failing
* several gcc10 x86 errors
* a checksum from kernel.org has changed

Now we have 3 different gcc10 yylloc patches:

gcc10-extern_YYLOC_global_declaration.patch:
    Linux < 4.2

linux4.2-gcc10-extern_YYLOC_global_declaration.patch:
    Linux 4.2+

linux4.17-gcc10-extern_YYLOC_global_declaration.patch:
    Linux 4.17+

[ci:skip-build]
[ci:ignore-count]
[ci:skip-vercheck]

Richard Qian authored 4 years ago and Oliver Smith committed 4 years ago

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

Use the dtb-appended kernel file, e.g. postmarketos-exynos4-dtb instead
of postmarketos-exynos4, if it is available. This is needed to flash a
mainline kernel with appended dtb to isorec devices.

Newbyte authored 4 years ago and Oliver Smith committed 4 years ago

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

Henrik Grimler authored 4 years ago and Oliver Smith committed 4 years ago

With these kernel sources the device boots successfully,
sometimes. Usually, kernel panics and device reboots a couple of
times, but after a few attempts (maybe 1, maybe 7) it succeeds to
boot. The problems seem to be related to FIMC IS, unfortunately it
does not seem to be possible to just disable it in the kernel config,
as that leads to compilation errors.

I have so far just experimented with getting wifi up and running, but
it does not work out of the box even after adding firmware package
with files from TheMuppets, wpa_supplicant fails to connect and dmesg
is filed with lines like:

```
[  112.509235]  [L0: wl_event_handle:  3109] CFG80211-INFO2) wl_escan_handler : Couldn't find P2PIE in probe response/beacon
```

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

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

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

Clayton Craft authored 4 years ago and Clayton Craft committed 4 years ago

This also includes a patch from Purism that is the best workaround so
far for the hang that plagues Dogwood phones.