Re: [U-Boot] [PATCH 2/2] rpi: expose the firmware provided FDT blob in ${fw_fdt_addr}

On 11/02/2016 12:06 PM, Cédric Schieli wrote: If the fw_boot_param saved at an early stage points to a valid FDT blob, let's expose it in ${fw_fdt_addr}. I'd suggest naming the variable dtb_addr not fw_fdt_addr. Both names are just as easy to use from custom U-Boot scripts, however certain

Re: [U-Boot] [PATCH 2/2] rpi: expose the firmware provided FDT blob in ${fw_fdt_addr}

On Wed, Nov 02, 2016 at 07:06:13PM +0100, Cédric Schieli wrote: > If the fw_boot_param saved at an early stage points to a valid FDT > blob, let's expose it in ${fw_fdt_addr}. > > Signed-off-by: Cédric Schieli OK, but how is fw_fdt_addr actually used? I think we need to

[U-Boot] [PATCH 2/2] rpi: expose the firmware provided FDT blob in ${fw_fdt_addr}

If the fw_boot_param saved at an early stage points to a valid FDT blob, let's expose it in ${fw_fdt_addr}. Signed-off-by: Cédric Schieli --- board/raspberrypi/rpi/rpi.c | 19 +++ 1 file changed, 19 insertions(+) diff --git a/board/raspberrypi/rpi/rpi.c