summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorJesper Nilsson <jesper.nilsson@axis.com>2010-08-02 17:48:31 +0200
committerJesper Nilsson <jesper.nilsson@axis.com>2010-08-04 12:59:43 +0200
commitb4973ae9dac3397499f5576c591d5c5bf51c68c6 (patch)
tree0bda0181f61cb50f8fd4c3507932e3b9f0b106dc
parentd77eab8cb18dc4b8adfa82088e95b48c654c66b9 (diff)
CRIS: Correct address of the romfs in boot image
The romfs should land after __init_end Signed-off-by: Jesper Nilsson <jesper.nilsson@axis.com>
-rw-r--r--arch/cris/arch-v10/kernel/head.S2
1 files changed, 1 insertions, 1 deletions
diff --git a/arch/cris/arch-v10/kernel/head.S b/arch/cris/arch-v10/kernel/head.S
index fc457710293..a1f2014b4e3 100644
--- a/arch/cris/arch-v10/kernel/head.S
+++ b/arch/cris/arch-v10/kernel/head.S
@@ -280,7 +280,7 @@ _no_romfs_in_flash:
;; the "rom fs" we'll possibly use in 2.4 if not JFFS (which does
;; not need this mechanism anyway)
- move.d __vmlinux_end, $r0; the image will be after the vmlinux end address
+ move.d __init_end, $r0; the image will be after the end of init
move.d [$r0], $r1 ; cramfs assumes same endian on host/target
cmp.d CRAMFS_MAGIC, $r1; magic value in cramfs superblock
bne 2f