The closed source RPI firmware modifies several entries in the
device-tree that are important for proper boot. The complete list
of these entries can be found at:
The function ft_board_setup() was modified so that if u-boot has
loaded a fdt that is different than the rpi fw fdt, then
it will copy all those important nodes and properties
created and modified by the rpi fw to the u-boot loaded fdt
blob.
Hi! Thank you for the notes! I have just submitted a amend for this commit and I changed the comments to correct the English mistakes. In my RPI4 seems to be working fine.
The closed source RPI firmware modifies several entries in the device-tree that are important for proper boot. The complete list of these entries can be found at:
https://forums.raspberrypi.com/viewtopic.php?p=1974233&hilit=firmware+device+tree+dma+ranges#p1974233
The function ft_board_setup() was modified so that if u-boot has loaded a fdt that is different than the rpi fw fdt, then it will copy all those important nodes and properties created and modified by the rpi fw to the u-boot loaded fdt blob.
Signed-off-by: Leonardo Amorim lam@vizrt.com