Skip to contentSkip to conversation

omap3_logic: Fix FDT ADDR for ramdisk booting

PATCH In review Adam Ford 2 participants 2 messages Mar 26, 2018 – Apr 7, 2018

lore
Share & tools
lore

Adam Ford

author
#0 lore raw

PATCH 1/1 omap3_logic: Fix FDT ADDR for ramdisk booting

The boot scripts for booting from ramdisk are using ${fdtimage} when they really should be using ${fdtaddr}

This patch will fix it so the RAMdisk bootscripts operate correctly.

include/configs/omap3_logic.h +2 -2
index c9a154c..162b05d 100644
@@ -153,10 +153,10 @@
 		"run loadramdisk\0" \
 	"mmcramboot=setenv bootfile uImage; " \
 		"run mmcrambootcommon; " \
-		"bootm ${loadaddr} ${rdaddr} ${fdtimage}\0" \
+		"bootm ${loadaddr} ${rdaddr} ${fdtaddr}\0" \
 	"mmcrambootz=setenv bootfile zImage; " \
 		"run mmcrambootcommon; " \
-		"bootz ${loadaddr} ${rdaddr} ${fdtimage}\0" \
+		"bootz ${loadaddr} ${rdaddr} ${fdtaddr}\0" \
 	"tftpboot=echo 'Booting kernel/ramdisk rootfs from tftp...'; " \
 		"run ramargs; " \
 		"run common_bootargs; " \
Signature · 1 line
2.7.4
#1 lore raw

include/configs/omap3_logic.h

Quoted 10 lines · Adam Ford

The boot scripts for booting from ramdisk are using ${fdtimage} when they really should be using ${fdtaddr}

This patch will fix it so the RAMdisk bootscripts operate correctly.

include/configs/omap3_logic.h +0 -0
index c9a154c..162b05d 100644

Applied to u-boot/master, thanks!

Signature · 8 lines
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20180406/b54e92d1/attachment.sig>