From: "Grant Likely" <grant.likely@secretlab.ca>
To: "Stephen Neuendorffer" <stephen.neuendorffer@xilinx.com>
Cc: scotwood@freescale.com, linuxppc-dev@ozlabs.org
Subject: Re: [RFC/PATCH v2] [POWERPC] bootwrapper: build multiple cuImages
Date: Fri, 1 Feb 2008 12:57:35 -0700 [thread overview]
Message-ID: <fa686aa40802011157m2b70205brae26157345331eb0@mail.gmail.com> (raw)
In-Reply-To: <20080201193225.67CFAAF0057@mail201-sin.bigfish.com>
On 2/1/08, Stephen Neuendorffer <stephen.neuendorffer@xilinx.com> wrote:
> What if it was something like:
>
> image-$(CONFIG_MPC832x_MDS) += cuImage.mpc832x_mds
> image-$(CONFIG_MPC832x_RDB) += cuImage.mpc832x_rdb
> image-$(CONFIG_MPC834x_ITX) += cuImage.mpc8349emitx \
> cuImage.mpc8349emitxgp
> platform-$(CONFIG_MPC83xx) += cuboot-83xx.o
>
> $(obj)/cuImage.%: vmlinux $(dtstree)/%.dts $(wrapperbits) $(platform-y)
> $(call if_changed,wrap,$(platform-y),(dtstree)/$*.dts)
>
> Which would eliminate making all the unnecessary bits of platform code
> and enabling the smart bits to be factored out of the wrapper? It would
> also make the dependency between the board and the platform code
> specific.It would also prevent building more than one platform at a
> time, but I don't think that's really possibly anyway?
It *is* possible, which is the goal of this patch.
:-D
There are only a few bits of non-multiplatform stuff left for 6xx
compatible platforms and those won't take too long to clear out.
The biggest part of the problem is the overloading of the cuImage.%
target. If the wrapper was encoded in the target then the problem
would go away. For example:
image-$(CONFIG_LITE5200) += cuImage-52xx.lite5200b
image-$(CONFIG_MPC832x_MDS) += cuImage-83xx.mpc832x_mds
image-$(CONFIG_MPC832x_RDB) += cuImage-83xx.mpc832x_rdb
image-$(CONFIG_MPC834x_ITX) += cuImage-83xx.mpc8349emitx \
cuImage-83xx.mpc8349emitxgp
And then have targets for each of the cuImage-<platform>.%, like so:
$(obj)/cuImage-52xx-%: vmlinux $(dtstree)/%.dts $(wrapperbits)
$(call if_changed,wrap,cuboot-52xx,(dtstree)/$*.dts)
$(obj)/cuImage-83xx-%: vmlinux $(dtstree)/%.dts $(wrapperbits)
$(call if_changed,wrap,cuboot-83xx,(dtstree)/$*.dts)
Cheers,
g.
--
Grant Likely, B.Sc., P.Eng.
Secret Lab Technologies Ltd.
next prev parent reply other threads:[~2008-02-01 19:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-01 0:07 [RFC/PATCH v2] [POWERPC] bootwrapper: build multiple cuImages Grant Likely
2008-02-01 19:32 ` Stephen Neuendorffer
2008-02-01 19:57 ` Grant Likely [this message]
2008-02-04 7:05 ` Fwd: " Grant Likely
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=fa686aa40802011157m2b70205brae26157345331eb0@mail.gmail.com \
--to=grant.likely@secretlab.ca \
--cc=linuxppc-dev@ozlabs.org \
--cc=scotwood@freescale.com \
--cc=stephen.neuendorffer@xilinx.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).