device/device-asus-me176c:
- Install me176c-factory to apply correct MAC addresses for
WiFi and BT
- Use FAT32 for boot partition. This allows flashing the boot
partition directly as ESP (EFI System Partition).
- Overall cleanup
device/linux-asus-me176c:
- Update kernel fork to 4.19.80
- Cleanup APKBUILD
- Stop building patched ACPI DSDT table directly into kernel
firmware/firmware-asus-me176c:
- Package WiFi firmware
firmware/firmware-asus-me176c-acpi:
- New package for the patched ACPI DSDT table
-> Separate from firmware-asus-me176c because it is always required,
(not optional)
[ci:skip-build]: runs into timeout
Without this, the device will simply run the broken ACPI DSDT table, so
we might as well update it. If we had put it into a subpackage, it
would not be possible to use the fixed DSDT without any other firmware
packages.
The changes in command line parameters of rmtfs mean: use the modem*
partitions directly (-P), in read-only mode (-r)...and it will boot the
modem automagically when ready (-s)
I've removed the udev rules in the rmtfs package because it doesn't look
like they are needed with those command line flags.
Mainline U-Boot looks for the device tree blob in the "second" area
of the Android boot image (see https://patchwork.ozlabs.org/patch/1025211/).
Add an option "deviceinfo_bootimg_dtb_second" to place the device DTB there.
Currently, the USB networking setup using configfs does not configure
a "serialnumber" for the USB gadget. This means that an empty
serial number will be sent during USB enumeration.
This is usually not a problem, but it seems to cause issues under
special circumstances (on asus-me176c on one of my PCs).
The USB Gadget configfs documentation also suggests setting
the "serialnumber":
https://www.kernel.org/doc/Documentation/usb/gadget_configfs.txt
It can be any string, so we can just set it as "postmarketOS" like
the manufacturer.
Turns out, that the pkgrel was bumped in Alpine. I had looked at an
outdated error message from the postmarketos-ui-* related MR and
assumed that this issue is still present (somwhat confused by the other
upstream-compat issues).
This reverts commit 07653d60a8.
Remove Werror workaround in APKBUILD, as the necessary change has been
upstreamed. By rebuilding the package, we fix the following errors:
Error relocating /usr/lib/preload/libsmdpkt_wrapper.so: minor: symbol not found
Error relocating /usr/lib/preload/libsmdpkt_wrapper.so: major: symbol not found
Package kcalcore has been renamed to kcalendarcore in Alpine.
pmbootstrap can't resolve kcalcore-dev anymore (not sure if this is a
bug in pmbootstrap, or if the -dev package is not properly replaced in
the upstream APKBUILD). Work around the resulting error by updating the
package to use the new dependency name.
Needs a pkgrel bump because dependency libboost was upgraded. This is
currently breaking everything depending on libphonenumber, for example
plasma mobile.
>>> postmarketos-ui-plasma-mobile: Analyzing dependencies...
ERROR: unsatisfiable constraints:
so:libprotobuf.so.20 (missing):
required by: libphonenumber-8.10.21-r0[so:libprotobuf.so.20]
>>> ERROR: postmarketos-ui-plasma-mobile: builddeps failed
The openrc service of lightdm has been moved to lightdm-openrc in
Alpine. Fix all UIs depending on lightdm, so their post-install script
does not fail with:
Executing postmarketos-ui-plasma-mobile-2-r6.post-install
* rc-update: service `lightdm' does not exist
It was forked to build the 5.17 pre-release, which is not needed
anymore. Remove now to unclutter pmaports, and to get pretty much all
remaining packages for x86_64 out of the queue on
build.postmarketos.org.
Bart Ribbers