linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: David Gibson <david@gibson.dropbear.id.au>
To: "Mark A. Greer" <mgreer@mvista.com>
Cc: linuxppc-dev <Linuxppc-dev@ozlabs.org>,
	Paul Mackerras <paulus@samba.org>
Subject: Re: [PATCH 1/13] powerpc: Add Makefile rules to wrap dts file in zImage
Date: Mon, 28 May 2007 14:43:31 +1000	[thread overview]
Message-ID: <20070528044331.GB5997@localhost.localdomain> (raw)
In-Reply-To: <20070525205014.GC20831@mag.az.mvista.com>

On Fri, May 25, 2007 at 01:50:14PM -0700, Mark A. Greer wrote:
> On Fri, May 25, 2007 at 11:33:59AM +1000, David Gibson wrote:
> > On Fri, May 25, 2007 at 11:32:42AM +1000, David Gibson wrote:
> > > On Thu, May 24, 2007 at 02:28:32PM -0700, Mark A. Greer wrote:
> > > > On Tue, May 22, 2007 at 10:23:49AM +1000, David Gibson wrote:
> 
> > > > > Just leave them out.  As long as you add the correct specific
> > > > > zImage.dts.% and zImage.dts_initrd.% targets to image-y and initrd-y,
> > > > > then a "make zImage" from the top-level Makefile will get them built.
> > > > 
> > > > That defeats the whole purpose of the patch--to allow the selection of
> > > > wrapping a dtb or not at build time.  Its just like initrd, you choose
> > > > whether to "do it" at build time.
> > > 
> > > Ah, right.  Remind me why that's useful again?
> > 
> > Sorry, to be more precise, why is that more useful than having "make
> > zImage" at the top level build both the dts and non-dts versions.
> 
> Well, that is a good question.  This is my reasoning which I put in the
> patch description:
> 
> 	"Having separate rules allows the user to choose whether to include
> 	a device tree--and which device tree--at build time.  This is
> 	useful when one Makefile target builds a zImage that runs on several
> 	platforms except for differing device trees.  By just setting
> 	CONFIG_DEVICE_TREE and running "make zImage.dts" the exact zImage
> 	you want is built without Makefile bloat or manually running the
> 	wrapper script."
> 
> Making both seems like a waste but its such a small waste that it
> doesn't really matter.  If you still object to this feature, I'll
> take it out since I (read: prpmc2800) doesn't really need this
> feature anyway.

Go with building both; that's consistent with the various other
platforms that build multiple images for different boot variants
(e.g. ppc64 builds powermac and pseries compatible images, Ebony
builds both cuImage and treeboot image).

-- 
David Gibson			| I'll have my music baroque, and my code
david AT gibson.dropbear.id.au	| minimalist, thank you.  NOT _the_ _other_
				| _way_ _around_!
http://www.ozlabs.org/~dgibson

  reply	other threads:[~2007-05-28  4:43 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-12  0:46 [PATCH 0/13] powerpc: Add support for Marvell/mv64x60 and prpmc2800 Mark A. Greer
2007-05-12  0:53 ` [PATCH 1/13] powerpc: Add Makefile rules to wrap dts file in zImage Mark A. Greer
2007-05-14  0:33   ` David Gibson
2007-05-14  3:46     ` Mark A. Greer
2007-05-14  3:49       ` David Gibson
2007-05-21 18:10     ` Mark A. Greer
2007-05-22  0:23       ` David Gibson
2007-05-24 21:28         ` Mark A. Greer
2007-05-25  1:32           ` David Gibson
2007-05-25  1:33             ` David Gibson
2007-05-25 20:50               ` Mark A. Greer
2007-05-28  4:43                 ` David Gibson [this message]
2007-05-12  0:54 ` [PATCH 2/13] powerpc: Add bootwrapper support for Marvell/mv64x60 hostbridge Mark A. Greer
2007-05-12  0:54 ` [PATCH 3/13] powerpc: Add bootwrapper support for Marvell MPSC Mark A. Greer
2007-05-12  0:54 ` [PATCH 4/13] powerpc: Add bootwrapper support for Marvell/mv64x60 I2C Mark A. Greer
2007-05-12  0:55 ` [PATCH 5/13] powerpc: Add interrupt support for Marvell mv64x60 chips Mark A. Greer
2007-05-12  0:55 ` [PATCH 6/13] powerpc: Create Marvell mv64x60 MPSC (serial) platform_data Mark A. Greer
2007-05-12  0:56 ` [PATCH 7/13] powerpc: Create Marvell mv64x60 ethernet platform_data Mark A. Greer
2007-05-12  0:56 ` [PATCH 8/13] powerpc: Create Marvell mv64x60 I2C platform_data Mark A. Greer
2007-05-12  0:57 ` [PATCH 9/13] powerpc: Add Marvell mv64x60 PCI bridge support Mark A. Greer
2007-05-12  0:57 ` [PATCH 10/13] powerpc: check cache coherency of kernel vs firmware Mark A. Greer
2007-05-14  0:40   ` David Gibson
2007-05-14 12:34     ` Segher Boessenkool
2007-05-14 14:44     ` Dale Farnsworth
2007-05-14 20:27       ` Mark A. Greer
2007-05-12  0:57 ` [PATCH 11/13] powerpc: Add DTS file for the Motorola PrPMC2800 platform Mark A. Greer
2007-05-12  0:58 ` [PATCH 12/13] powerpc: Add bootwrapper support for " Mark A. Greer
2007-05-12  0:58 ` [PATCH 13/13] powerpc: Add arch/powerpc support for the Motorola PrPMC2800 Mark A. Greer
  -- strict thread matches above, loose matches on Subject: below --
2007-05-10 20:02 [PATCH 0/13] powerpc: Add support for Marvell/mv64x60 and prpmc2800 Mark A. Greer
2007-05-10 20:04 ` [PATCH 1/13] powerpc: Add Makefile rules to wrap dts file in zImage Mark A. Greer
2007-05-10 23:29   ` David Gibson
2007-05-11 15:59     ` Mark A. Greer

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=20070528044331.GB5997@localhost.localdomain \
    --to=david@gibson.dropbear.id.au \
    --cc=Linuxppc-dev@ozlabs.org \
    --cc=mgreer@mvista.com \
    --cc=paulus@samba.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).