[PATCH v1 1/1] sandbox: swap bloblist and fdt loading address sequence

[Tom Rini]

On Fri, Mar 07, 2025 at 12:16:29PM +0200, Svyatoslav Ryhel wrote:

> The existing memory layout places the bloblist at 0xb000 and the fdt at 0x100,
> resulting in a 0xaf00 size constraint for the fdt. This constraint has been
> reached. Lets modify the layout by moving the bloblist to 0x100. With a
> bloblist size limit of 0x400, this allows the fdt to be positioned at 0x500,
> thus expanding its permissible size.
> 
> Signed-off-by: Svyatoslav Ryhel <clamor95 at gmail.com>
[snip]
> diff --git a/doc/arch/sandbox/sandbox.rst b/doc/arch/sandbox/sandbox.rst
> index a8b0d7f0395..99459815c25 100644
> --- a/doc/arch/sandbox/sandbox.rst
> +++ b/doc/arch/sandbox/sandbox.rst
> @@ -658,8 +658,8 @@ that are mapped into that memory:
>  ========   ========================   ===============================
>  Addr       Config                     Usage
>  ========   ========================   ===============================
> -     100   CONFIG_SYS_FDT_LOAD_ADDR   Device tree
> -    b000   CONFIG_BLOBLIST_ADDR       Blob list
> +     100   CONFIG_BLOBLIST_ADDR       Blob list
> +     500   CONFIG_SYS_FDT_LOAD_ADDR   Device tree
>     10000   CFG_MALLOC_F_ADDR          Early memory allocation
>     f0000   CONFIG_PRE_CON_BUF_ADDR    Pre-console buffer
>    100000   TCG Event log              TCG Event Log

My question is do we have room or not to set aside 512KiB (as the
"should never be this large" value) instead of not quite 64KiB which we
can possibly hit again in the not too distant future? I think I checked
earlier and CFG_MALLOC_F_ADDR + CONFIG_SYS_MALLOC_F_LEN should still fit
below CONFIG_PRE_CON_BUF_ADDR if we do that (and also give the bloblist
some room to expand).

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