summaryrefslogtreecommitdiff
path: root/scripts
diff options
context:
space:
mode:
authorJonas Karlman <[email protected]>2026-08-11 23:16:49 +0000
committerTom Rini <[email protected]>2026-08-24 13:58:00 -0600
commit94a09715bf4c8dfdefbefcd341d0c9da04c5a6c1 (patch)
tree1175494cf5f5d078a12c28eb75257538eb1e89a3 /scripts
parent480644c06e202abec58543aec502f218939fff1e (diff)
boot: image-fdt: Restore suppression of irrelevant ERROR message
The commit 623f6c5b6ab7 ("boot: image-fdt: free old dtb reservations") removed the suppression of ERROR messages when -EINVAL was returned due to the memory region not being part of the LMB memory map. This causes an irrelevant ERROR message during boot, e.g.: Model: Radxa ROCK 3B [...] ERROR: reserving fdt memory region failed (addr=10f000 size=100 flags=2): -22 or Model: Rockchip RK3288 Asus Tinker Board S [...] ERROR: reserving fdt memory region failed (addr=fe000000 size=1000000 flags=4): -22 FDT correctly contains reserved-memory for 10f000 or fe000000 and U-Boot correctly does not make these regions available in the LMB memory map: memory[0] [0x200000-0xefffffff], 0xefe00000 bytes, flags: none memory[1] [0x100000000-0x1ffffffff], 0x100000000 bytes, flags: none or memory[0] [0x0-0x7fffffff], 0x80000000 bytes, flags: none With lmb_alloc_mem() and lmb_free() both returning -EFAULT when the requested memory region is not part of the LMB memory map it should be safe to ignore these errors when FDT memreserve and reserved-memory is being processed. Print -EFAULT errors using a debug message to restore suppression of this irrelevant ERROR message when memory region is not part of the LMB memory map. Fixes: 623f6c5b6ab7 ("boot: image-fdt: free old dtb reservations") Signed-off-by: Jonas Karlman <[email protected]> Reviewed-by: Randolph Sapp <[email protected]>
Diffstat (limited to 'scripts')
0 files changed, 0 insertions, 0 deletions