Comment # 8 on bug 1208173 from Aaron Puchert

(In reply to Chester Lin from comment #4)
> It seems that preload FDT [fdtcontroladdr] owned by VF2 firmware blobs does
> not match the reviewing DTs in upstream, which is adopted by the contrib
> project.

Would this be solved by using a different firmware image?

> Could you try the following instructions?
> 
> ---
> StarFive # load mmc 1:3 ${fdt_addr_r}
> /boot/dtb/jh7110-starfive-visionfive-2-vb.dtb
> 20801 bytes read in 8 ms (2.5 MiB/s)
> StarFive # load mmc 1:1 ${kernel_addr_r} /EFI/BOOT/bootriscv64.efi
> 2846720 bytes read in 123 ms (22.1 MiB/s)
> StarFive # fdt addr ${fdt_addr_r}
> StarFive # fdt rsvmem add 0x40000000 0x1000
> StarFive # bootefi ${kernel_addr_r} ${fdt_addr_r}
> ---
> 
> Since the current image has not supported FW booting via SDIO, I will fix
> the manual installation in Wiki, thanks for your feedback!

This works, thanks!

(In reply to Chester Lin from comment #6)
> Thanks! Since the DISTRO_DEFAULTS feature has been enabled by VF2 u-boot,
> the simplified u-boot instructions are:
> 
> # load mmc 1:3 ${fdt_addr_r} /boot/dtb/<va-or-vb-dtb-file>
> # fdt addr ${fdt_addr_r}; fdt rsvmem add 0x40000000 0x00001000
> # boot

Also works.