Saving the fdt address in uboot for later use by the kernel kind of seems to work, not sure if by accident, or something might have changed in the meantime, because, contrary to what the uboot menuconfig entry states:
No such variable exist, which would suggest that the fdt is not being passed on to uboot by the Pi firmware. However, there is a correct fdt blob stored in a different address that is held by a different variable:Using that address the kernel is no longer reporting the error above.
Code:
CONFIG_SAVE_PREV_BL_FDT_ADDR:When u-boot is used as a chain-loaded bootloader (replacing OS kernel), enable this option to save fdt address, passed by the previous bootloader for future use.Address is saved to 'prevbl_fdt_addr' environment variable.If no fdt was provided by previous bootloader, no env variables will be created.
Code:
fdtcontroladdr=3972aea0
Statistics: Posted by nowave7 — Thu Dec 26, 2024 10:02 pm