[PATCH] lmb: Reinstate access to memory above ram_top

[Tom Rini]

On Fri, Mar 13, 2026 at 10:06:15PM +0100, Jonas Karlman wrote:
> 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/

Ah oops, I thought it had all been merged. I see Kever's tag on it, I'll
grab it directly right away. Sorry about that!

-- 
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 228 bytes
Desc: not available
URL: <https://lists.denx.de/pipermail/u-boot/attachments/20260313/a81073c9/attachment.sig>