The Ten64 board runs a U-Boot which works best directly
booting EFI. Attempting to load your own DTB or other steps
will cause issues.
(see https://ten64doc.traverse.com.au/faq/#common-issues)
The current stable Ten64 firmware unfortunately searches for
boot.scr before bootaa64.efi. So redirect it back to the EFI path.
A future Ten64 firmware package will prefer EFI first before
any boot script avoiding this issue. I will provide a patch
reversing this when that day comes.
Signed-off-by: Mathew McBride <matt@traverse.com.au>
Reviewed-by: Michael Tremer <michael.tremer@ipfire.org>
+# Traverse Ten64 board can boot EFI directly
+# Redirect it to the EFI process already in the
+# bootloader
+# (Remove on release of the 1.x Ten64 firmwire package)
+if test "${board}" = "ten64"; then
+ load ${devtype} ${devnum}:2 ${kernel_addr_r} efi/boot/bootaa64.efi
+ bootefi ${kernel_addr_r} ${fdt_addr_r}
+fi;
+
if test ${boot_dev} = ""; then
setenv boot_dev mmc;
setenv root_dev /dev/mmcblk0p3;