configs: db820c: set bootm_size
PATCH 1/1 configs: db820c: set bootm_size
set bootm_size to the memory available to safely contain a kernel, device tree and initrd for relocation.
--- include/configs/dragonboard820c.h | 1 + 1 file changed, 1 insertion(+)
include/configs/dragonboard820c.h +1 -0
@@ -48,6 +48,7 @@"ramdisk_addr_r=0x91000000\0" \"scriptaddr=0x90000000\0" \"pxefile_addr_r=0x90100000\0" \ +"bootm_size=0x8000000" \BOOTENV /* Size of malloc() pool */
Signature · 1 line
2.17.1
PATCH 1/1 configs: db820c: set bootm_size
Quoted 13 lines · Jorge Ramirez-Ortiz
set
bootm_sizeto the memory available to safely contain a kernel, device tree and initrd for relocation.Signed-off-by Jorge Ramirez-Ortiz <[email protected]>--- include/configs/dragonboard820c.h | 1 + 1 file changed, 1 insertion(+)include/configs/dragonboard820c.h +0
-0
include/configs/dragonboard820c.h line 54
Quoted 7 lines
include/configs/dragonboard820c.h +1
-0@@ -48,6 +48,7 @@"ramdisk_addr_r=0x91000000\0" \"scriptaddr=0x90000000\0" \"pxefile_addr_r=0x90100000\0" \ +"bootm_size=0x8000000" \BOOTENV /* Size of malloc() pool */
We need to also remove fdt_high while we do this. And per the email I sent out today it would be good to audit the rest of the variables wrt booti (in this case) usage. It would be good to confirm we don't want to have initrd relocation. In the case of this platform, I would strongly encourage that as it places the initrd below the fdt and kernel and there is a long history of reports of problems later on with large initrds stomping over things, or being stomped over (load initrd, load fdt, load kernel, raw initrd support so kernel fails to find valid initrd is the failure). Thanks!
Signature · 8 lines
Tom -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: not available URL: <https://lists.denx.de/pipermail/u-boot/attachments/20200129/a9d9d0a2/attachment.sig>