From: Scott Wood <scottwood@freescale.com>
To: Grant Likely <grant.likely@secretlab.ca>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [RFC] [POWERPC] bootwrapper: build multiple cuImages
Date: Thu, 31 Jan 2008 10:00:42 -0600 [thread overview]
Message-ID: <20080131160042.GA24370@ld0162-tx32.am.freescale.net> (raw)
In-Reply-To: <fa686aa40801301840k3d9a9ba2n251d2cdb9e659748@mail.gmail.com>
On Wed, Jan 30, 2008 at 07:40:28PM -0700, Grant Likely wrote:
> mpc866ads, mpc885ads and ep88xc are oddities in that they build
> zImages with embedded device tree blobs.
What about ep8248e? And the mpc8xxads boards use cuImage, not zImage.
> One option would be to add two new targets: zImage.dtb.% and
> zImage.initrd.dtb.%, but I'm not sure if it is a good idea.
I'd much prefer that over having several lines per board in the makefile.
-Scott
next prev parent reply other threads:[~2008-01-31 16:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-31 0:34 [RFC] [POWERPC] bootwrapper: build multiple cuImages Grant Likely
2008-01-31 1:49 ` Stephen Neuendorffer
2008-01-31 2:40 ` Grant Likely
2008-01-31 16:00 ` Scott Wood [this message]
2008-01-31 17:22 ` Grant Likely
2008-01-31 10:21 ` Jochen Friedrich
2008-01-31 21:12 ` Geoff Levand
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=20080131160042.GA24370@ld0162-tx32.am.freescale.net \
--to=scottwood@freescale.com \
--cc=grant.likely@secretlab.ca \
--cc=linuxppc-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).