From: "Grant Likely" <grant.likely@secretlab.ca>
To: linuxppc-dev@ozlabs.org,
"Josh Boyer" <jwboyer@linux.vnet.ibm.com>,
"Kumar Gala" <galak@kernel.crashing.org>
Subject: Re: [RFC/PATCH] powerpc/bootwrapper: Allow user to specify additional default targets
Date: Fri, 4 Jul 2008 00:51:44 -0600 [thread overview]
Message-ID: <fa686aa40807032351l631febe2h8d38a9eed1053b6b@mail.gmail.com> (raw)
In-Reply-To: <20080701175852.32575.39707.stgit@trillian.secretlab.ca>
Anyone had a chance to look at this? I think this could be used to
eliminate a lot of the platform specific default targets in
arch/powerpc/boot/Makefile by moving them into the defconfigs. Josh,
Kumar, what are your thoughts?
g.
On Tue, Jul 1, 2008 at 11:59 AM, Grant Likely <grant.likely@secretlab.ca> wrote:
> From: Grant Likely <grant.likely@secretlab.ca>
>
> It is inconvenient to add additional default targets to the bootwrapper
> Makefile for each new board supported which just needs a different dts
> file. This change allows the defconfig to specify additional build
> targets.
>
> Signed-off-by: Grant Likely <grant.likely@secretlab.ca>
> ---
>
> arch/powerpc/Kconfig | 13 +++++++++++++
> arch/powerpc/boot/Makefile | 3 +++
> 2 files changed, 16 insertions(+), 0 deletions(-)
>
> diff --git a/arch/powerpc/Kconfig b/arch/powerpc/Kconfig
> index 3934e26..f09f617 100644
> --- a/arch/powerpc/Kconfig
> +++ b/arch/powerpc/Kconfig
> @@ -458,6 +458,19 @@ config CMDLINE
> some command-line options at build time by entering them here. In
> most cases you will need to specify the root device here.
>
> +config EXTRA_TARGETS
> + string "Additional default image types"
> + help
> + List additional targets to be built by the bootwrapper here (separated
> + by spaces). This is useful for targets that depend of device tree
> + files in the .dts directory.
> +
> + Targets in this list will be build as part of the default build
> + target, or when the user does a 'make zImage' or a
> + 'make zImage.initrd'.
> +
> + If unsure, leave blank
> +
> if !44x || BROKEN
> config ARCH_WANTS_FREEZER_CONTROL
> def_bool y
> diff --git a/arch/powerpc/boot/Makefile b/arch/powerpc/boot/Makefile
> index 1cee2f9..1e38237 100644
> --- a/arch/powerpc/boot/Makefile
> +++ b/arch/powerpc/boot/Makefile
> @@ -270,6 +270,9 @@ ifeq ($(CONFIG_PPC32),y)
> image-$(CONFIG_PPC_PMAC) += zImage.coff zImage.miboot
> endif
>
> +# Allow extra targets to be added to the defconfig
> +image-y += $(subst ",,$(CONFIG_EXTRA_TARGETS))
> +
> initrd- := $(patsubst zImage%, zImage.initrd%, $(image-n) $(image-))
> initrd-y := $(patsubst zImage%, zImage.initrd%, \
> $(patsubst dtbImage%, dtbImage.initrd%, \
>
>
--
Grant Likely, B.Sc., P.Eng.
Secret Lab Technologies Ltd.
next prev parent reply other threads:[~2008-07-04 6:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-01 17:59 [RFC/PATCH] powerpc/bootwrapper: Allow user to specify additional default targets Grant Likely
2008-07-04 6:51 ` Grant Likely [this message]
2008-07-07 13:18 ` Josh Boyer
2008-07-07 13:34 ` Grant Likely
2008-07-07 14:07 ` Josh Boyer
2008-07-07 14:29 ` Grant Likely
2008-07-09 14:00 ` Josh Boyer
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=fa686aa40807032351l631febe2h8d38a9eed1053b6b@mail.gmail.com \
--to=grant.likely@secretlab.ca \
--cc=galak@kernel.crashing.org \
--cc=jwboyer@linux.vnet.ibm.com \
--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).