From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: "Joachim Förster" <JOFT@gmx.de>
Cc: linuxppc-dev@lists.ozlabs.org,
"Florian Vögel" <fvoegel@partner.ime-actia.de>,
"Guillaume Dargaud" <dargaud@lpsc.in2p3.fr>
Subject: Re: Where is CONFIG_BOOT_LOAD ?
Date: Thu, 14 Apr 2011 12:52:07 +1000 [thread overview]
Message-ID: <1302749527.28876.107.camel@pasglop> (raw)
In-Reply-To: <4DA485CD.6060604@gmx.de>
On Tue, 2011-04-12 at 19:03 +0200, Joachim Förster wrote:
> Note that the default 0x400... is the link address of the zImage
> wrapper
> rather than the one of THE kernel.
>
> Currently the link address seems to be hard-coded into
> arch/powerpc/boot/wrapper
> (a shell script). Since long ago I'm wondering why the maintainers
> did
> that. But I guess there is a reason, because it wasn't that way in
> the
> old arch/ppc days ;-) ...
>
> Is configuring the zImage-piggy-back-loader through menuconfig & co
> evil?
Well, not really evil but if you need a special setting for your board,
you add a case for that board in the wrapper script. The idea is that
the boot wrapper can be build outside of the kernel build tree itself.
IE. A distro could (and sometimes do) ship with the standalone boot
directory, possibly the .o's already built, and will "wrap" the zImage
at install time.
Cheers,
Ben.
next prev parent reply other threads:[~2011-04-14 2:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-08 9:28 Where is CONFIG_BOOT_LOAD ? Guillaume Dargaud
2011-04-08 9:42 ` Florian Vögel
2011-04-08 12:58 ` Guillaume Dargaud
2011-04-12 17:03 ` Joachim Förster
2011-04-14 2:52 ` Benjamin Herrenschmidt [this message]
2011-04-14 9:18 ` Guillaume Dargaud
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=1302749527.28876.107.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=JOFT@gmx.de \
--cc=dargaud@lpsc.in2p3.fr \
--cc=fvoegel@partner.ime-actia.de \
--cc=linuxppc-dev@lists.ozlabs.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.