[PATCH v7 0/7] Relocate U-Boot in the last bank

Tom Rini trini at konsulko.com
Thu Jun 25 17:18:29 CEST 2026


On Wed, 17 Jun 2026 10:48:18 +0300, Ilias Apalodimas wrote:

> There was a discussion recently on the mailing lists regarding our
> management of memory above ram_top [0]. The tl;dr is that we have two problems.
> 
> The first one is that U-Boot always relocates to the top of the first available
> bank unless there's special board code to sidestep that. The second is we don't
> successfully deal with devices that can only do 32-bit DMA.
> 
> [...]

Applied to u-boot/next, thanks!

[1/7] treewide: move bi_dram[] from bd to gd
      commit: 1174c99ab421168221be372bd83a4143bf5f167d
[2/7] common: move ram_base calculation to independent INITCALL()
      commit: 15b35e4289e11f1ab201701dfb6dc0232b30be48
[3/7] common: Clean up setup_dest_addr()
      commit: 0943f107ce4adb47d4b01c06e046dce130a1de50
[4/7] rpi: Add a local get_effective_memsize()
      commit: d19d9e1c064b6c782959d1da7bddf1e9da1c55d4
[5/7] common: Add an option to relocate on ram top
      commit: 55a34217698491cc0bb8d53d630644dc8756629c
[6/7] configs: Enable RELOC_ADDR_TOP on arm64 QEMU
      commit: aefd4a769bb6727978c408ff24b93ba9047d535d
[7/7] doc: Add a warning about using RELOC_ADDR_TOP
      commit: fb537c85bca0e3d29a62fe119181bf1744b8c91a
-- 
Tom




More information about the U-Boot mailing list