summaryrefslogtreecommitdiff
path: root/board/samsung
diff options
context:
space:
mode:
authorYe Li <ye.li@nxp.com>2020-05-05 20:28:38 +0800
committerStefano Babic <sbabic@denx.de>2020-05-10 20:55:20 +0200
commit7c351ff5e0e50359d9feb49272650bd01417f721 (patch)
tree58c3dc3c1a3dd0edad98b6413ffcb9d3b110df73 /board/samsung
parentf44afd546f6236479581469e1fb969c9ce9f9eac (diff)
imx: imx8qm/qxp: Fix issue in get_effective_memsize
When Trusty OS allocates the mem region from 0xfe0000000-0xffffffff, the get_effective_memsize does not return correct memory size. There is a check in get_effective_memsize to find the memreg where the u-boot is running, and return the size of that memreg as the result of get_effective_memsize. When using aligned start, the value is 0x80200000 since it is 2MB aligned. Thus the finding of memreg will fail and return the PHYS_SDRAM_1_SIZE because u-boot text base is 0x80020000. This cause u-boot is relocated to the high memory where has been occupied by Trusty OS. Reviewed-by: Peng Fan <peng.fan@nxp.com> Signed-off-by: Ye Li <ye.li@nxp.com> Signed-off-by: Peng Fan <peng.fan@nxp.com>
Diffstat (limited to 'board/samsung')
0 files changed, 0 insertions, 0 deletions