aboutsummaryrefslogtreecommitdiff
path: root/arch/riscv/conf/boot.cmd
diff options
context:
space:
mode:
authorKimplul <kimi.h.kuparinen@gmail.com>2021-08-25 23:47:08 +0300
committerKimplul <kimi.h.kuparinen@gmail.com>2021-08-25 23:47:08 +0300
commit5dfac4879ce5f34503ae7537eefd3fc48d6fa750 (patch)
tree7ac25f1a14373ae08ea6aa2406d8f83026dba74a /arch/riscv/conf/boot.cmd
parentb235f49f31d11e68019c42f48b6641c37e4c986e (diff)
downloadkmi-5dfac4879ce5f34503ae7537eefd3fc48d6fa750.tar.gz
kmi-5dfac4879ce5f34503ae7537eefd3fc48d6fa750.zip
libfdt seems to work
At least as far as reading memory info, cool. One issue I have is that .(ro)data is apparently accessed by absolute addresses, so I need to know at which address the kernel is going to be loaded. I would prefer completely position independent code, but if that's not possible then eh.
Diffstat (limited to 'arch/riscv/conf/boot.cmd')
-rw-r--r--arch/riscv/conf/boot.cmd6
1 files changed, 4 insertions, 2 deletions
diff --git a/arch/riscv/conf/boot.cmd b/arch/riscv/conf/boot.cmd
index ddbc319..782c1e8 100644
--- a/arch/riscv/conf/boot.cmd
+++ b/arch/riscv/conf/boot.cmd
@@ -1,2 +1,4 @@
-fatload ${devtype} ${devnum} ${kernel_addr_r} apos.itb
-bootm ${kernel_addr_r}
+fdt move ${fdt_addr} ${fdt_addr_r}
+fdt addr ${fdt_addr_r}
+load ${devtype} ${devnum} ${kernel_addr_r} apos.itb
+bootm ${kernel_addr_r} - ${fdt_addr_r}