[PATCH] lmb: Reinstate access to memory above ram_top

Jonas Karlman jonas at kwiboo.se
Fri Mar 13 22:06:15 CET 2026


Hi Tom,

On 3/13/2026 9:54 PM, Tom Rini wrote:
> On Wed, 28 Jan 2026 00:48:40 +0100, Marek Vasut wrote:
> 
>> Revert commit eb052cbb896f ("lmb: add and reserve memory above ram_top")
>> and commit 1a48b0be93d4 ("lmb: prohibit allocations above ram_top even from
>> same bank"). These are based on incorrect premise of the first commit, that
>> "U-Boot does not use memory above ram_top". While U-Boot itself indeed does
>> not and should not use memory above ram_top, user can perfectly well use
>> that memory from the U-Boot shell, for example to load content in there.
>>
>> [...]
> 
> Applied to u-boot/next, thanks!

This patch break RK356x devices with 8 GiB RAM until following patch
also has been applied, currently only the fix for RK3588 got applied to
next.

"rockchip: rk3568: Include all addressable DRAM in memory map"
https://patchwork.ozlabs.org/project/uboot/patch/20260309210234.521070-1-jonas@kwiboo.se/

Regards,
Jonas

> 
> [1/1] lmb: Reinstate access to memory above ram_top
>       commit: a3075db94d49f415658bf7e961e1eae90d9abc33



More information about the U-Boot mailing list