Add more modules to initfs, so that it can detect rootfs on nvme
drive, use usb keyboard and get display properly initialized during
initramfs stage.
Withouth those panel/display is not properly initialized, root partition
cannot be found if it is on nvme drive, and on top of that USB keyboard
is not working, so you can't even debug it from initramfs.
Add myself as co-maintainer of package.
Signed-off-by: Alexey Minnekhanov <alexeymin@postmarketos.org>
Part-of: <https://gitlab.postmarketos.org/postmarketOS/pmaports/-/merge_requests/9203>
Was 5 years ago disabled because most apps weren't marked as adaptive.
But that clearly has changed today and remaining apps should be updated
upstream.
That means that some apps might "disappear" when existing installations
had un-adaptive apps, but given the button on the button that is easy to
read, I consider that fine.
This reverts commit ae02ad9190 ("main/postmarketos-ui-phosh: disable app drawer filtering (MR 2298)")
Part-of: <https://gitlab.postmarketos.org/postmarketOS/pmaports/-/merge_requests/8954>
The reason why we have patches instead of a separate repo are because of
the following reasons:
1. We don't want to make a repo to which users contribute to. While
people haven't tried to commit to my repository yet, this is
yet another incentive for people to upstream into Linux kernel
mainline. Most of the functionality is here. We just need to
upstream it.
2. I assume that all the patches here aren't needed. This calls
for a scream test. People who find functionalality missing will
open an issue. It becomes trivial to add/remove patches from
the `source=...` var rather than repackaging the entire kernel.
The next commit aims to remove a lot of patches and see if there
are people who rely on said functionality. If not, there is no
requirement to upstream it.
Signed-off-by: Rudraksha Gupta <guptarud@gmail.com>
Part-of: <https://gitlab.postmarketos.org/postmarketOS/pmaports/-/merge_requests/9136>
This is a bootloader for Open Firmware PowerPC systems that we will use
to replace grub-ieee1275 in device-generic-ppc64le. Due to its use of
RUSTC_BOOTSTRAP, this APKBUILD cannot go to Alpine at the moment, but
once the Rust targets are added upstream, this can be moved to aports.
Part-of: <https://gitlab.postmarketos.org/postmarketOS/pmaports/-/merge_requests/9002>
Federico recently contacted me and asked me to take over maintainership,
as he wants to shift his focus entirely to the Moto Edge 30. I returned
to working on the Nothing Phone (1) a couple of weeks ago, so I was
happy to accept.
With their consent, I have also added Eugene and Vasiliy, as they
actively contribute to the development of kernel support for the device
and will be able to test upcoming updates.
Signed-off-by: Danila Tikhonov <danila@mainlining.org>
Firmware blobs were extracted from the latest
NothingOS V3.2-260618-1045 EOL build.
Also add the board-2 blob required for Wi-Fi calibration.
Signed-off-by: Danila Tikhonov <danila@mainlining.org>
Currently, loading the a630 firmware files fails in the iniramfs
when the display is manually configured. This firmware is loaded
once the rootfs is loaded and the gpu is polled, but the error
messages clog the early boot logs and can make parsing them much
harder. Because of this, and because these devices don't have an
issue with bootimg size, including the firmware is a QOL change.
Signed-off-by: Aster Boese <asterboese@mailbox.org>
Part-of: <https://gitlab.postmarketos.org/postmarketOS/pmaports/-/merge_requests/8649>
Currently, loading the a630 firmware files fails in the iniramfs
when the display is manually configured. This firmware is loaded
once the rootfs is loaded and the gpu is polled, but the error
messages clog the early boot logs and can make parsing them much
harder. Because of this, and because these devices don't have an
issue with bootimg size, including the firmware is a QOL change.
Signed-off-by: Aster Boese <asterboese@mailbox.org>
Part-of: <https://gitlab.postmarketos.org/postmarketOS/pmaports/-/merge_requests/8649>
Currently, loading the a630 firmware files fails in the iniramfs
when the display is manually configured. This firmware is loaded
once the rootfs is loaded and the gpu is polled, but the error
messages clog the early boot logs and can make parsing them much
harder. Because of this, and because these devices don't have an
issue with bootimg size, including the firmware is a QOL change.
Signed-off-by: Aster Boese <asterboese@mailbox.org>
Part-of: <https://gitlab.postmarketos.org/postmarketOS/pmaports/-/merge_requests/8649>
Aelin