From: ext-mika.1.westerberg@nokia.com (Mika Westerberg)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/8] Initial implementation of kdump for ARM
Date: Fri, 23 Apr 2010 07:53:13 +0300 [thread overview]
Message-ID: <20100423045313.GH3028@esdhcp04058.research.nokia.com> (raw)
In-Reply-To: <20100423042626.GA2997@localhost.localdomain>
On Fri, Apr 23, 2010 at 06:26:26AM +0200, ext Janboe Ye wrote:
> These are some other hard code address in some boards.
>
> For example, beagle board boot_params is 0x80000100.
>
> I guest nokia's Nseris does not use atags for transfering params.
>
> When I test my relocated kernel, it blocks at machinee initialization.
>
> Maybe there is other address mapping issue. I will look it tomorrow.
Yes, we use atags.
I have following changes on top of these patches. Note that you should also
change beagles board file so that it works with different PHYS_OFFSET (if you
are going to pass initrd, then that will need to be changed also).
I actually have beagleboard in home and I can try it there as well but I'll be
away weekend so it is going to happen earliest on monday.
Thanks,
MW
diff --git a/arch/arm/mach-omap2/Makefile.boot b/arch/arm/mach-omap2/Makefile.boot
index 565aff7..b958007 100644
--- a/arch/arm/mach-omap2/Makefile.boot
+++ b/arch/arm/mach-omap2/Makefile.boot
@@ -1,3 +1,8 @@
- zreladdr-y := 0x80008000
+ifeq ($(CONFIG_CRASH_DUMP),y)
+zreladdr-y := 0x84008000
+params_phys-y := 0x84000100
+else
+zreladdr-y := 0x80008000
params_phys-y := 0x80000100
+endif
initrd_phys-y := 0x80800000
diff --git a/arch/arm/plat-omap/include/plat/memory.h b/arch/arm/plat-omap/include/plat/memory.h
index 9ad41dc..596a130 100644
--- a/arch/arm/plat-omap/include/plat/memory.h
+++ b/arch/arm/plat-omap/include/plat/memory.h
@@ -40,7 +40,15 @@
#define PHYS_OFFSET UL(0x10000000)
#elif defined(CONFIG_ARCH_OMAP2) || defined(CONFIG_ARCH_OMAP3) || \
defined(CONFIG_ARCH_OMAP4)
+/*
+ * We want crashdump kernels to be in different physical address than
+ * the primary kernel.
+ */
+#ifdef CONFIG_CRASH_DUMP
+#define PHYS_OFFSET UL(0x84000000)
+#else
#define PHYS_OFFSET UL(0x80000000)
+#endif /* CONFIG_CRASH_DUMP */
#endif
/*
diff --git a/arch/arm/mach-omap2/board-omap3beagle.c b/arch/arm/mach-omap2/board-omap3beagle.c
index df5c918..a023f62 100644
--- a/arch/arm/mach-omap2/board-omap3beagle.c
+++ b/arch/arm/mach-omap2/board-omap3beagle.c
@@ -459,7 +459,7 @@ MACHINE_START(OMAP3_BEAGLE, "OMAP3 Beagle Board")
/* Maintainer: Syed Mohammed Khasim - http://beagleboard.org */
.phys_io = 0x48000000,
.io_pg_offst = ((0xfa000000) >> 18) & 0xfffc,
- .boot_params = 0x80000100,
+ .boot_params = PHYS_OFFSET + 0x100,
.map_io = omap3_beagle_map_io,
.init_irq = omap3_beagle_init_irq,
.init_machine = omap3_beagle_init,
next prev parent reply other threads:[~2010-04-23 4:53 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-20 8:50 [PATCH 0/8] Initial implementation of kdump for ARM Mika Westerberg
2010-04-20 8:50 ` [PATCH 1/8] arm: kdump: reserve memory for crashkernel Mika Westerberg
2010-04-20 8:50 ` [PATCH 2/8] arm: kdump: implement crash_setup_regs() Mika Westerberg
2010-04-20 8:50 ` [PATCH 3/8] arm: kdump: implement machine_crash_shutdown() Mika Westerberg
2010-04-20 8:50 ` [PATCH 4/8] arm: kdump: skip indirection page when crashing Mika Westerberg
2010-04-20 8:50 ` [PATCH 5/8] arm: kdump: implement copy_oldmem_page() Mika Westerberg
2010-04-20 8:50 ` [PATCH 6/8] arm: allow passing an ELF64 header to elf_check_arch() Mika Westerberg
2010-04-20 8:50 ` [PATCH 7/8] arm: kdump: add support for elfcorehdr= parameter Mika Westerberg
2010-04-20 8:50 ` [PATCH 8/8] arm: kdump: add CONFIG_CRASH_DUMP Kconfig option Mika Westerberg
2010-04-22 12:03 ` [PATCH 0/8] Initial implementation of kdump for ARM Mika Westerberg
2010-04-23 3:05 ` Janboe Ye
2010-04-23 4:11 ` Mika Westerberg
2010-04-23 4:26 ` Janboe Ye
2010-04-23 4:53 ` Mika Westerberg [this message]
2010-04-27 10:05 ` Mika Westerberg
2010-04-26 1:26 ` Joonyoung Shim
2010-04-26 9:16 ` Mika Westerberg
2010-05-03 8:28 ` Mika Westerberg
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20100423045313.GH3028@esdhcp04058.research.nokia.com \
--to=ext-mika.1.westerberg@nokia.com \
--cc=linux-arm-kernel@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).