Add uboot-tools, uboot-images-armv8, bcm283x-firmware to enable us to support devices such as the Raspberry Pi 3 and Pine64.
Signed-off-by: Peter Robinson pbrobinson@gmail.com
Pull-Request has been merged by ausil
One question; will these devices actually be using libostree's uboot backend? There are definitely non-Fedora users of that but this would be the first Fedora use of it, correct? Was it tested?
No, on aarch64 we use grub2-efi, but the u-boot implements uEFI so it boots u-boot -> grub2 -> linux.
We need u-boot and the firmware so people can setup the devices to actually boot.
Hah, OK. Just briefly though then - in this scenario does classical grubby update the grub2 config? And u-boot is actually an EFI binary or something? If there's a link to more information about this setup (or perhaps an interactive shell? I briefly glanced at https://fedoraproject.org/wiki/Test_Machine_Resources_For_Package_Maintainers but it looks like there's no aarch64 )
grubby
I suppose at some point I need to get one of these boxes to actually play with it locally.
It's the exact same process used for all other grub efi upgrades.
U-boot it not an EFI binary, it's a firmware/bios (similar to say EDK2/tianocore EFI reference implementation used in the virt stacks), it had the ability to execute EFI binaries such as shim/grub2 etc, it can run shell and I believe now even passes a bunch of the EFI testsuite.
It works on a RPi3 or Pine64 and will for a bunch more SBCs in F-28, feel free to msg me directly about anything else, prob a bit off topic for this ticket
Add uboot-tools, uboot-images-armv8, bcm283x-firmware to enable us
to support devices such as the Raspberry Pi 3 and Pine64.
Signed-off-by: Peter Robinson pbrobinson@gmail.com