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: jdl@jdl.com, linuxppc-dev <Linuxppc-dev@ozlabs.org>
Subject: Re: [PATCH/RFC] Add cmd_wrap_dts rules to arch/powerpc/boot/Makefile
Date: Sat, 13 Jan 2007 10:00:47 +1100	[thread overview]
Message-ID: <20070112230047.GC18201@localhost.localdomain> (raw)
In-Reply-To: <20070111004048.GA27351@mag.az.mvista.com>

On Wed, Jan 10, 2007 at 05:40:48PM -0700, Mark A. Greer wrote:
> On Thu, Oct 19, 2006 at 12:51:56PM -0700, Mark A. Greer wrote:
> > On Thu, Oct 19, 2006 at 09:03:18AM -0500, Jon Loeliger wrote:
> > > So, like, the other day "Mark A. Greer" mumbled:
> > > > 
> > > > This would be used by the sandpoint, say, by adding the following rules
> > > > to the Makefile in the appropriate places:
> > > > 
> > > > 	$(obj)/zImage.sandpoint: vmlinux $(wrapperbits)
> > > > 		$(call cmd,wrap_dts,sandpoint)
> > > > 
> > > > 	$(obj)/zImage.initrd.sandpoint: vmlinux $(wrapperbits)
> > > > 		$(call cmd,wrap_dts_initrd,sandpoint)
> > > > 
> > > > and:
> > > > 
> > > > 	image-$(CONFIG_SANDPOINT)               += zImage.sandpoint
> > > > 
> > > > Comments?
> > > 
> > > Isn't there a way to do this without hardcoding the
> > > platform name in the makefiles directly?  I fear for
> > > the one-per-platform effect that is yet to come with
> > > the conversion of many of the legacy boards.
> 
> Okay, its been a while so let's see if anyone remembers and/or cares
> anymore.  :)
> 
> How about something like the patch below?
> 
> Basically, if you want a dtb wrapped up in your zImage, set
> CONFIG_DEFAULT_DTB=y and also define CONFIG_DTS to point where your dts
> file is.
> 
> Does that meet everyones requirements?

Erm.. actually from what I could tell, the way the wrapper script
invokes dtc will make a mess if you're building with a different
object tree from the source tree.  I think the other suggested patches
which have a cmd_wrap_dtb and a spearate make rule to invoke dtc are a
better shot, and it might be a good idea to rip the dtc invocation out
of wrapper entirely.

-- 
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

      parent reply	other threads:[~2007-01-12 23:00 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-19  0:26 [PATCH/RFC] Add cmd_wrap_dts rules to arch/powerpc/boot/Makefile Mark A. Greer
2006-10-19  0:34 ` Josh Boyer
2006-10-19  5:50 ` Matthew McClintock
2006-10-19  5:58   ` Matthew McClintock
2006-10-19 19:26   ` Mark A. Greer
2006-10-19 14:03 ` Jon Loeliger
2006-10-19 19:51   ` Mark A. Greer
2007-01-11  0:40     ` Mark A. Greer
2007-01-12 19:50       ` Jon Loeliger
2007-01-12 21:48         ` Mark A. Greer
2007-01-12 23:00       ` David Gibson [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=20070112230047.GC18201@localhost.localdomain \
    --to=david@gibson.dropbear.id.au \
    --cc=Linuxppc-dev@ozlabs.org \
    --cc=jdl@jdl.com \
    --cc=mgreer@mvista.com \
    /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).