[PATCH v1 1/2] sandbox: vbe: size firmware1 area to fit the binman fw-update section
Simon Glass
sjg at chromium.org
Tue Jun 23 16:50:21 CEST 2026
On 2026-06-21T14:39:32, Aristo Chen <aristo.chen at canonical.com> wrote:
> sandbox: vbe: size firmware1 area to fit the binman fw-update section
>
> The firmware1 node in test.dts declares area-size = 0xe00000 (14 MiB)
> but the binman fw-update section in sandbox_vpl.dtsi is 0x2000000
> (32 MiB) and the FIT inside it carries ~16 MiB of external data
> (spl + u-boot subimages). The FIT therefore extends past the
> declared firmware area, contradicting the documented contract of
> vbe_read_fit() that the FIT must fit within @area_size.
>
> The mismatch was tolerated because no caller actually bounded the
> external-data load against area_size. Bring the devicetree in line
> with the binman section size so the FIT extent stays within the
> trusted firmware area, in preparation for vbe_read_fit() enforcing
> that bound.
>
> state-offset and version-offset are left as-is; they were already
> inside the FIT data region and are not exercised by test_vbe_vpl.
>
> Signed-off-by: Aristo Chen <aristo.chen at canonical.com>
>
> arch/sandbox/dts/test.dts | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
Reviewed-by: Simon Glass <sjg at chromium.org>
More information about the U-Boot
mailing list