Correct a comment... the stack used by ubldr is the same stack u-boot was

running on when it jumped to the ubldr entry point.  None of the arches
that use this code set up a different stack in their start.S routines.

1 files changed, 3 insertions, 1 deletions

diff --git a/sys/boot/uboot/common/main.c b/sys/boot/uboot/common/main.c
index 3b97a6eadd51..c4efb1f69bd9 100644
--- a/sys/boot/uboot/common/main.c
+++ b/sys/boot/uboot/common/main.c
@@ -416,7 +416,9 @@ main(int argc, char **argv)
 
 	/*
 	 * Initialise the heap as early as possible.  Once this is done,
-	 * alloc() is usable. The stack is buried inside us, so this is safe.
+	 * alloc() is usable.  We are using the stack u-boot set up near the top
+	 * of physical ram; hopefully there is sufficient space between the end
+	 * of our bss and the bottom of the u-boot stack to avoid overlap.
 	 */
 	uboot_heap_start = round_page((uintptr_t)end);
 	uboot_heap_end   = uboot_heap_start + 512 * 1024;