From: Matthew McClintock <msm@freescale.com>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: linuxppc-dev <Linuxppc-dev@ozlabs.org>
Subject: Re: [HACK] add sandpoint + flattened dt support to arch/powerpc/boot
Date: Thu, 18 May 2006 08:52:01 -0500 [thread overview]
Message-ID: <1147960321.7607.9.camel@localhost.localdomain> (raw)
In-Reply-To: <1147930376.17679.72.camel@localhost.localdomain>
Do you have any comments about how you envision updating the "virtual"
mode image with information passed from the boot loader? I am asking
this from the standpoint of updating the "virtual" flat tree with
correct values, in order to boot from older firmware.
-Matthew
On Thu, 2006-05-18 at 15:32 +1000, Benjamin Herrenschmidt wrote:
> That is why, I think, what we should do is have rules for building
> separate zImage wrappers. The basic OF one (which exists in both real
> and virtual mode versions and that I'd like to make capable of also
> working if a flat device-tree is passed in), the zImage.sandpoint, the
> zImage.prep, and whatever...
>
next prev parent reply other threads:[~2006-05-18 13:52 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-18 0:21 [HACK] add sandpoint + flattened dt support to arch/powerpc/boot Mark A. Greer
2006-05-18 5:32 ` Benjamin Herrenschmidt
2006-05-18 13:52 ` Matthew McClintock [this message]
2006-05-26 6:03 ` Benjamin Herrenschmidt
2006-05-23 0:58 ` Mark A. Greer
2006-05-23 1:13 ` Tom Rini
2006-07-19 20:02 ` Guennadi Liakhovetski
2006-07-19 22:10 ` Mark A. Greer
2006-07-19 22:29 ` Guennadi Liakhovetski
2006-07-20 0:39 ` Mark A. Greer
2006-06-14 3:37 ` Mark A. Greer
2006-05-18 13:47 ` Matthew McClintock
2006-05-19 0:37 ` Mark A. Greer
2006-05-19 0:49 ` Michael Ellerman
2006-05-22 22:22 ` Tom Rini
2006-06-05 20:41 ` Matthew McClintock
2006-06-05 21:04 ` Tom Rini
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=1147960321.7607.9.camel@localhost.localdomain \
--to=msm@freescale.com \
--cc=Linuxppc-dev@ozlabs.org \
--cc=benh@kernel.crashing.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).