From: Matthew McClintock <msm@freescale.com>
To: "Mark A. Greer" <mgreer@mvista.com>
Cc: linuxppc-dev <Linuxppc-dev@ozlabs.org>,
Paul Mackerras <paulus@samba.org>
Subject: Re: [PATCH/RFC] Add cmd_wrap_dts rules to arch/powerpc/boot/Makefile
Date: Thu, 19 Oct 2006 00:50:01 -0500 [thread overview]
Message-ID: <1161237001.4992.5.camel@localhost> (raw)
In-Reply-To: <20061019002635.GA2356@mag.az.mvista.com>
On Wed, 2006-10-18 at 17:26 -0700, Mark A. Greer wrote:
>
> $(obj)/zImage.sandpoint: vmlinux $(wrapperbits)
> $(call cmd,wrap_dts,sandpoint)
>
> $(obj)/zImage.initrd.sandpoint: vmlinux $(wrapperbits)
> $(call cmd,wrap_dts_initrd,sandpoint)
Can you do something like this to make it even more automatic:
$(obj)/$(CONFIG_SANDPOINT): vmlinux $(wrapperbits)
$(call cmd,wrap_dts,`echo $CONFIG_SANDPOINT | awk '{print substr($1, 8)}'`)
I'm not sure if this will work exactly as is. But, I do think adding an
entry in the Makefile for every possible bootwrapper target is needed. I
say this because I intend to add targets for all variants of Freescale
boards at some point in the future.
Let me clarify my needs here some more, I want to be able to type 'make
cuImage' and have the scripts build the wrapper target and attached the
correct dtb for all variants of Freescale boards. Of course, the dtb
will hopefully be specified in the defconfig. Does this make sense?
-Matthew
next prev parent reply other threads:[~2006-10-19 5:50 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 [this message]
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
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=1161237001.4992.5.camel@localhost \
--to=msm@freescale.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.