u-boot.git/board/raspberrypi/rpi, branch master

rpi: Update the naming for bcm2712 SoC RevD naming

2026-03-26T08:29:48+00:00

The downstream Raspberry Pi uses two namings for the revD
SoC device trees, both bcm2712d0-rpi-5-b and bcm2712-d-rpi-5-b
but it seems upstream has settled on just the later, so lets
use that as it's the name that maps both upstream and downstream.

Fixes: c15a7919725 ("board/raspberrypi: add bcm2712d0-rpi-5-b for Raspberry Pi 5")
Signed-off-by: Peter Robinson 
Reviewed-by: Matthias Brugger

board/raspberrypi: add bcm2712d0-rpi-5-b for Raspberry Pi 5

2026-03-12T12:11:24+00:00

This commit adds an FDT entry for the d0 stepping of the BCM2712 SoC.
This entry is used by the v1.1 revision of the board
(revision & 0x0f == 1).

Signed-off-by: Filip Kokosiński 
Reviewed-by: Peter Robinson 
Tested-by: Peter Robinson

board/raspberrypi: add multi-FDT support

2026-03-12T12:11:24+00:00

This patch adds support for multiple FDT files per board model. This is
done by adding the FDTFILES macro, which initializes two rpi_model
struct members: fdtfiles and fdtcount.

The new-style revision codes designate LSB bits as board revision; this
value is used to choose between provided FDTs. The first element of the
fdtfiles list is used should no revision match.

Signed-off-by: Filip Kokosiński 
Reviewed-by: Peter Robinson 
Tested-by: Peter Robinson

rpi: pass the Video Core logs DT parameter through

2026-03-12T12:02:59+00:00

Pass the VC logs DT parameter through to the kernel
device tree. This is used by the vclog tool and is
a useful debugging tool.

Signed-off-by: Peter Robinson 
Acked-by: Matthias Brugger

rpi: Fix DRAM size reporting to show total RAM

2025-11-28T13:50:51+00:00

The VideoCore mailbox GET_ARM_MEMORY only reports the size of the
first accessible memory region (~947 MiB on RPi4 with 8GB), not the
total RAM. This causes U-Boot to display "DRAM: 947 MiB (total 7.9 GiB)"
instead of "DRAM: 7.9 GiB".

On Raspberry Pi 4 with 8GB RAM, the memory is split across multiple
non-contiguous banks. The dram_init() function only sets gd->ram_size
to the first bank size reported by the VideoCore firmware, while
fdtdec_setup_memory_banksize() correctly populates all memory banks
from the device tree.

Fix this by updating gd->ram_size after dram_init_banksize() has
populated all memory banks, so it reflects the actual total RAM
across all banks.

Signed-off-by: Anders Roxell 
Reviewed-by: Peter Robinson

rpi: Use the U-Boot control FDT for fdt_addr

2025-11-25T09:22:12+00:00

The fdt_addr variable is used in extlinux as a fallback devicetree if
none is provided by the boot command. Otherwise the only use in U-Boot
seems to me efi_install_fdt() when the internal FDT is required.

The existing mechanism uses the devicetree provided to U-Boot, but in
its original, unrelocated position. In my testing on an rpi_4, this ends
up at 2b35ef00 which is not a convenient place in memory, if the ramdisk
is large.

U-Boot already deals with this sort of problem by relocating the FDT
to a safe address.

So use the control-FDT address instead.

Remove the existing comment, which is confusing, since the FDT is not
actually passed unmodified to the kernel: U-Boot adds various things
using its FDT-fixup mechanism.

Note that board_get_usable_ram_top() reduces the RAM top for boards with
less RAM. This behaviour is left unchanged as there is no other
mechanism for U-Boot to handle this.

Signed-off-by: Simon Glass 
Reviewed-by: Christopher Obbard 
Tested-by: Christopher Obbard  # CM4 1G

rpi: Fix compilation with larger configs

2025-11-25T09:22:12+00:00

Tom reports that adding more Kconfig options fails with
board/raspberrypi/rpi/lowlevel_init.o: in function `save_boot_params':
board/raspberrypi/rpi/lowlevel_init.S:20:(.text+0x0):
relocation truncated to fit: R_AARCH64_ADR_PREL_LO21
against symbol `fw_dtb_pointer' defined in .data section
in board/raspberrypi/rpi/rpi.o
make: *** [Makefile:2029: u-boot] Error 1

Since fw_dtb_pointer lives in .data it might end up above the
+-1MB that adr can reach.
So switch over to adrp+add which has a +-4gb reach.

Reported-by: Tom Rini 
Closes: https://source.denx.de/u-boot/custodians/u-boot-raspberrypi/-/issues/2
Signed-off-by: Ilias Apalodimas 
Reviewed-by: Peter Robinson

rpi: Update environment to support booti and large initrd

2025-04-16T10:00:50+00:00

The existing values don't provide for decompressing an arm64 boot-image.
Add those values and move things apart a bit so that a 50MB kernel can be
accommodated.

Signed-off-by: Simon Glass 
Reviewed-by: Christopher Obbard 
Tested-by: Christopher Obbard  # CM4 1G
Reviewed-by: Christopher Obbard 
Tested-by: Christopher Obbard  # CM4 1G

rpi: Drop fdt_high and initrd_high

2025-04-16T10:00:50+00:00

These are not needed now since there is a bootm_size setting to keep
things within the lower part of memory.

Drop them.

Signed-off-by: Simon Glass 
Reviewed-by: Tom Rini 
Suggested-by: Tom Rini 
Reviewed-by: Christopher Obbard 
Tested-by: Christopher Obbard  # CM4 1G
Reviewed-by: Christopher Obbard 
Tested-by: Christopher Obbard  # CM4 1G

rpi: Set bootm_size to 512MB

2025-04-16T10:00:49+00:00

Set this option so that all boot images stay within the bottom 512MB of
memory. This should allow us to drop the fdt_high and initrd_high
options.

Signed-off-by: Simon Glass 
Reviewed-by: Tom Rini 
Suggested-by: Tom Rini 
Reviewed-by: Christopher Obbard 
Tested-by: Christopher Obbard  # CM4 1G