From: Simon Richter <Simon.Richter@hogyros.de>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: linuxppc-dev list <linuxppc-dev@ozlabs.org>,
linuxppc64-dev <linuxppc64-dev@ozlabs.org>
Subject: Re: powerpc boot sequence rework
Date: Tue, 22 Nov 2005 16:26:43 +0100 [thread overview]
Message-ID: <438338B3.5000301@hogyros.de> (raw)
In-Reply-To: <1132645967.26560.221.camel@gaston>
[-- Attachment #1: Type: text/plain, Size: 673 bytes --]
Hi,
Benjamin Herrenschmidt wrote:
> Here's a quick review of what happens now before my intended changes and
> some hilights of the ppc32/ppc64 differences. I intentionally ignored
> APUS as I don't even pretend to understand what it does, it will have to
> adapt to our changes anyway :)
Heh. I was anticipating this since the Oldenburg meeting.
> - Very early trampoline code from the firmware (prom_init/bootx_init)
> that could eventually be moved to a boot wrapper but is currently kept
> in the kernel for convenience.
That answers my question whether I should have the code that builds the
flattened device tree in the kernel or in the bootloader.
Simon
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 307 bytes --]
prev parent reply other threads:[~2005-11-22 15:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-22 7:52 powerpc boot sequence rework Benjamin Herrenschmidt
2005-11-22 15:26 ` Simon Richter [this message]
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=438338B3.5000301@hogyros.de \
--to=simon.richter@hogyros.de \
--cc=benh@kernel.crashing.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=linuxppc64-dev@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 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).