summaryrefslogtreecommitdiff
path: root/src/apps/http
diff options
context:
space:
mode:
authorYe Li <[email protected]>2026-04-16 21:48:38 +0800
committerPeng Fan <[email protected]>2026-05-06 10:29:33 +0800
commit33ff22c0b169401ab555e8508c06da1848a2d539 (patch)
tree3485fb1381220e230fa18db56a459f1a72a46449 /src/apps/http
parent34127dff316085df27fefe040f83756602183099 (diff)
arm: layerscape: Check zero size memory bank before lmb_add
In layerspace's lmb_arch_add_memory implementation, all memory bank are added to lmb, even some is with zero size. This will cause lmb treating it as overlap with available memory by lmb_addrs_overlap and merge with available memory. Finally causing available memory start address changed to 0. For example, on LX2160, before zero memory bank added to lmb, there are two available memory regions: - region 0, start 0x80000000, size 0x7be00000 - region 1, start 0x2080000000, size 0x700000000 After zero size memory bank added, merge to one region: - region 0, start 0, size 0x2780000000 This wrong new region causes efi_memory_init issue when allocating bounce buffer because of conflict address (with uboot reserved) is allocated. Signed-off-by: Ye Li <[email protected]> Reviewed-by: Peng Fan <[email protected]> Signed-off-by: Peng Fan <[email protected]>
Diffstat (limited to 'src/apps/http')
0 files changed, 0 insertions, 0 deletions