<samueldr>
note that u-boot can manage EFI boot on non-GPT, MBR disks too
<samueldr>
so these steps are not needed, though they are one way to do ut
<samueldr>
it*
<samueldr>
as for getting started? you could in theory just burn a mainline u-boot to an sd card, without an os on it, and no os on the internal storage of the device if it has one
<samueldr>
then use the iso image for aarch64
<samueldr>
you will need to handle the reserved for u-boot carefully, though, which is why I liked making a hole in the GPT
<samueldr>
with that hole, as long as I don't zero (wipe) the GPT, but only manipulate partitions, everything should stay put
lopsided98 has quit [Quit: No Ping reply in 180 seconds.]
lopsided98 has joined #nixos-aarch64
<cornu>
thanks, i'm trying to boot nixos on the espressobin. The aarch64 iso image uses extlinux?, but extlinux support is broken in the marvel uboot used in the espressobin.
<cornu>
thanks for the allwinner gpt example, i will try with a gpt partition
<samueldr>
this image is just like the x86_64 equivalent
<samueldr>
grub as a uefi bootloader
<samueldr>
it's built using the same expression
<cornu>
thanks, perfect
<samueldr>
should work on EBBR/SBBR too
<samueldr>
it does work with tianocore on the rpi3
<samueldr>
considering the rpi4 will soon have a working tianocore, it's getting exciting for that too
<samueldr>
(it technically already can work, but you have to use the type-c port for usb in tianocore, since they haven't written drivers yet for the PCIe side of the rpi4)
<samueldr>
(so you have to power the rpi4 through other means)
<cornu>
whats EBBR/SBBR?
<cornu>
ah just googled
<samueldr>
EBBR is likely the more relevant one
<samueldr>
and it's a subset (iirc) of how sbbr works
<samueldr>
basically specs out how much of UEFI arm devices should use (when they follow the spec)
<samueldr>
and how device-specifics should be stored so a single image can be shared