Raspberry firmware used to pass a FDT blob at a fixed address (0x100), but this is not true anymore. The address now depends on both the memory size and the blob size [1].
If one wants to passthrough this FDT blob to the kernel, the most reliable way is to save its address from the r2 register passed to U-Boot in the entry point and expose it in a environment variable for further processing. [1] https://www.raspberrypi.org/forums//viewtopic.php?f=107&t=134018 Cédric Schieli (2): rpi: save firmware provided boot param for later use rpi: expose the firmware provided FDT blob in ${fw_fdt_addr} board/raspberrypi/rpi/Makefile | 1 + board/raspberrypi/rpi/lowlevel_init.S | 26 ++++++++++++++++++++++++++ board/raspberrypi/rpi/rpi.c | 19 +++++++++++++++++++ include/configs/rpi.h | 4 ++++ 4 files changed, 50 insertions(+) create mode 100644 board/raspberrypi/rpi/lowlevel_init.S -- 2.7.3 _______________________________________________ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot