From: Milton Miller <miltonm@bga•com>
To: David Gibson <david@gibson•dropbear.id.au>
Cc: ppcdev <linuxppc-dev@ozlabs•org>,
Guillaume Dargaud <dargaud@lpsc•in2p3.fr>
Subject: Re: Calling the kernel from a mini-bootloader
Date: Fri, 18 Jul 2008 12:47:08 -0500 [thread overview]
Message-ID: <fc7a47590d1991616768ecd10cfc032a@bga.com> (raw)
In-Reply-To: <20080718034727.GF18748@yookeroo.seuss>
On Jul 17, 2008, at 10:47 PM, David Gibson wrote:
> On Thu, Jul 17, 2008 at 11:14:11AM -0500, Milton Miller wrote:
>> On Thu Jul 17 at 23:22:28 EST in 2008, Guillaume Dargaud wrote:
> [snip]
[more snip]
>> We call this the flattened device tree.
>
> Your firmware doesn't have to deal with this though, although it can.
> It's perfectly acceptable - in fact I'd mildly recommend it over doing
> this in the firmware - to instead have the kernel's zImage wrapper
> supply the flattened device tree, folding information it needs to get
> from the firmware into it.
I thought about adding a section on which to recommend or talk about
the tradeoffs, but got hungry and hit send before going to lunch.
Yes, I the zImage choice is definitely the least amount of code to
write, and is a good tradeoff to get future upgradability. It may not
be the absolute fastest split of the work to start the kernel but it is
reasonably good, especially as it will decompress the kernel to its
run-time destination.
milton
next prev parent reply other threads:[~2008-07-18 17:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-17 16:14 Calling the kernel from a mini-bootloader Milton Miller
2008-07-18 3:47 ` David Gibson
2008-07-18 17:47 ` Milton Miller [this message]
2008-07-18 8:43 ` Guillaume Dargaud
2008-07-18 18:38 ` Milton Miller
2008-07-22 10:49 ` Guillaume Dargaud
2008-07-22 16:01 ` Guillaume Dargaud
-- strict thread matches above, loose matches on Subject: below --
2008-07-17 13:22 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=fc7a47590d1991616768ecd10cfc032a@bga.com \
--to=miltonm@bga$(echo .)com \
--cc=dargaud@lpsc$(echo .)in2p3.fr \
--cc=david@gibson$(echo .)dropbear.id.au \
--cc=linuxppc-dev@ozlabs$(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