From: Johannes Weiner <jw@emlix.com>
To: Chris Zankel <chris@zankel.net>
Cc: Oskar Schirmer <os@emlix.com>, Daniel Gloeckner <dg@emlix.com>,
linux-kernel@vger.kernel.org
Subject: [patch 7/8] xtensa: let platform override KERNELOFFSET
Date: Tue, 10 Mar 2009 12:56:50 +0100 [thread overview]
Message-ID: <20090310120632.078480048@emlix.com> (raw)
In-Reply-To: 20090310115643.653120649@emlix.com
[-- Attachment #1: 0006-xtensa-let-platform-override-KERNELOFFSET.patch --]
[-- Type: text/plain, Size: 786 bytes --]
The linker script should not assume a fix offset in memory for the
kernel, this is platform-specific, so let the platform set it.
Signed-off-by: Johannes Weiner <jw@emlix.com>
---
arch/xtensa/kernel/vmlinux.lds.S | 3 +++
1 file changed, 3 insertions(+)
--- a/arch/xtensa/kernel/vmlinux.lds.S
+++ b/arch/xtensa/kernel/vmlinux.lds.S
@@ -17,6 +17,7 @@
#include <asm-generic/vmlinux.lds.h>
#include <variant/core.h>
+#include <platform/hardware.h>
OUTPUT_ARCH(xtensa)
ENTRY(_start)
@@ -26,7 +27,9 @@ jiffies = jiffies_64 + 4;
jiffies = jiffies_64;
#endif
+#ifndef KERNELOFFSET
#define KERNELOFFSET 0xd0001000
+#endif
/* Note: In the following macros, it would be nice to specify only the
vector name and section kind and construct "sym" and "section" using
--
next prev parent reply other threads:[~2009-03-10 13:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-10 13:11 [patch 0/8] xtensa: s6000 & s6105 Johannes Weiner
2009-03-10 11:56 ` [patch 1/8] xtensa: nommu support Johannes Weiner
2009-03-10 11:56 ` [patch 2/8] xtensa: variant-specific code Johannes Weiner
2009-03-10 11:56 ` [patch 3/8] xtensa: variant irq set callbacks Johannes Weiner
2009-03-10 11:56 ` [patch 4/8] xtensa: s6000 variant core definitions Johannes Weiner
2009-03-10 11:56 ` [patch 5/8] xtensa: s6000 variant Johannes Weiner
2009-03-10 11:56 ` [patch 6/8] xtensa: s6000 gpio driver Johannes Weiner
2009-03-10 11:56 ` Johannes Weiner [this message]
2009-03-10 11:56 ` [patch 8/8] xtensa: platform stretch s6105 eval board Johannes Weiner
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=20090310120632.078480048@emlix.com \
--to=jw@emlix.com \
--cc=chris@zankel.net \
--cc=dg@emlix.com \
--cc=linux-kernel@vger.kernel.org \
--cc=os@emlix.com \
/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