From: Geoff Levand <geoffrey.levand@am•sony.com>
To: Kumar Gala <galak@kernel•crashing.org>
Cc: linuxppc-dev@ozlabs•org, Paul Mackerras <paulus@samba•org>
Subject: Re: [PATCH] [POWERPC] bootwrapper: Allow specifying of image physical offset
Date: Fri, 07 Mar 2008 17:44:19 -0800 [thread overview]
Message-ID: <47D1EF73.7030200@am.sony.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0803071055200.8522@blarg.am.freescale.net>
On 03/07/2008 08:55 AM, Kumar Gala wrote:
> Normally we assume kernel images will be loaded at offset 0. However
> there are situations, like when the kernel itself is running at a non-zero
> physical address, that we don't want to load it at 0.
>
> Allow the wrapper to take an offset. We use this when building u-boot images.
>
> Signed-off-by: Kumar Gala <galak@kernel•crashing.org>
> ---
> arch/powerpc/boot/Makefile | 7 +++++++
> arch/powerpc/boot/wrapper | 12 ++++++++++--
> 2 files changed, 17 insertions(+), 2 deletions(-)
>
> diff --git a/arch/powerpc/boot/Makefile b/arch/powerpc/boot/Makefile
> index f43dd6e..1b4bfc6 100644
> --- a/arch/powerpc/boot/Makefile
> +++ b/arch/powerpc/boot/Makefile
> @@ -35,6 +35,12 @@ endif
>
> BOOTCFLAGS += -I$(obj) -I$(srctree)/$(obj) -I$(srctree)/$(src)/libfdt
>
> +ifdef CONFIG_MEMORY_START
> +MEMBASE=$(CONFIG_MEMORY_START)
We have the powerpc config option CONFIG_KERNEL_START. I'm
wondering how this CONFIG_MEMORY_START is different. I just
did a quick search, and it seems that CONFIG_MEMORY_START is
only defined for the renesas arch's.
-Geoff
next prev parent reply other threads:[~2008-03-08 1:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-07 16:55 [PATCH] [POWERPC] bootwrapper: Allow specifying of image physical offset Kumar Gala
2008-03-08 1:44 ` Geoff Levand [this message]
2008-03-08 15:13 ` Kumar Gala
2008-03-11 0:37 ` David Gibson
2008-03-11 4:19 ` Kumar Gala
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=47D1EF73.7030200@am.sony.com \
--to=geoffrey.levand@am$(echo .)sony.com \
--cc=galak@kernel$(echo .)crashing.org \
--cc=linuxppc-dev@ozlabs$(echo .)org \
--cc=paulus@samba$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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