New comment by Calandracas606 on void-packages repository

https://github.com/void-linux/void-packages/pull/46563#issuecomment-1756008296

Comment:
> > Any changes needed on the image creation side of things? In principal, no opposition.
> 
> Yes, will do this on the weekend. Not sure if we even want to keep the creation of a pbp specific image. A generic aarch64 efi image should boot just fine (which is still missing on mklive), and we could just suggest users to have a uboot (or towboot) on their SPI.

Agreed.

TowBoot's sentiment is that [the distribution shouldn't be managing the firmware used to boot the system.](https://tow-boot.org/FAQ.html)

Additionally, I believe that the u-boot image that we distribute isn't ideal, and has some problems with "suspend to ram" (or rockchip's fake suspend to ram). I haven't completely pinned that issue down to our u-boot image, but it was resolved when I switched to [megi's u-boot images and rk2aw bootloader](https://xnux.eu/rk2aw/).

Ultimately, I am of the opinion that it should be up to the user to install and manage their own boot-loader.

Having a generic aarch64 image is likely best, generating an appropriate extlinux

I have a successfully running pbp musl, using rk2aw in SPI, megi's uboot on emmc, generic base-system, linux, u-boot-menu + pinebookpro-firmware. In the past, I've had success booting with Towboot -> grub -> EFI