Reviewed-by: Michael Tremer <michael.tremer(a)ipfire.org>

> On 3 Oct 2022, at 07:20, Mathew McBride <matt(a)traverse.com.au> wrote:
> 
> 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(a)traverse.com.au>
> ---
> config/u-boot/boot.cmd | 9 +++++++++
> 1 file changed, 9 insertions(+)
> 
> diff --git a/config/u-boot/boot.cmd b/config/u-boot/boot.cmd
> index 64e9c05bc..a27996780 100644
> --- a/config/u-boot/boot.cmd
> +++ b/config/u-boot/boot.cmd
> @@ -1,3 +1,12 @@
> +# 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;
> -- 
> 2.30.1
>