From: David Gibson <david@gibson.dropbear.id.au>
To: Scott Wood <scottwood@freescale.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH 5/6] bootwrapper: Add a cuImage target.
Date: Sat, 24 Mar 2007 10:39:27 +1100 [thread overview]
Message-ID: <20070323233927.GD4459@localhost.localdomain> (raw)
In-Reply-To: <20070323151836.GC6060@ld0162-tx32.am.freescale.net>
On Fri, Mar 23, 2007 at 10:18:36AM -0500, Scott Wood wrote:
> On Fri, Mar 23, 2007 at 04:40:48PM +1100, David Gibson wrote:
> > > +cuboot-plats :=
> > > +src-plat := of.c $(cuboot-plats:%=cuboot-%.c)
> >
> > Rather than this special cuboot-plats stuff, I suggest you just list
> > each cuboot platform in src-plat independently.
>
> OK, I suppose the number of platforms will be few enough for that.
>
> > We can also git rid of the need for a CONFIG option specifying the dts
> > (and thereby taking us back to the one-config-per-board era) by using
> > rules like:
> >
> > $(obj)/uImage.83xx.%: vmlinux $(wrapperbits) $(srctree)/$(src)/dts/%.dts
> > $(call if_changed,wrap,cuboot-83xx,$(srctree)/$(src)/dts/$*)
>
> But then you can't build with an out-of-tree dts. It's not a huge deal,
> but still... What's wrong with a config option?
Because it takes us back to reconfigure the kernel for each different
device tree, even though both the vmlinux and the zImage can run
happily on multiple device trees.
> > And to get the right things built use something like:
> > image-$(CONFIG-83xx) += $(mpx83xx-boards:%=uImage.83xx.%)
>
> And then I'd have to determine which boards are supported by the kernel
> that was built, so I don't trick the user into thinking that valid images
> were produced for every single 83xx. I'd also have to enumerate every
> single board in the makefile, which would suck.
Hrm, yeah that is a bit sucky. Could we use a wildcard? Or make
per-platform subdirectories of arch/powerpc/boot/dts?
> > Or optionally add a batch of bool config options for each board
> > variant.
>
> I don't want to do that. There shouldn't have to be a 1-1 correspondence
> between each dts file and anything in the kernel.
Yeah, fair enough.
--
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
next prev parent reply other threads:[~2007-03-23 23:39 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-22 19:46 [PATCH 0/6] bootwrapper/cuboot Scott Wood
2007-03-22 19:49 ` [PATCH 1/6] bootwrapper: Add dt_xlate_reg(), and use it to find serial registers Scott Wood
2007-03-22 19:49 ` [PATCH 2/6] bootwrapper: Add ppcboot.h Scott Wood
2007-03-22 19:49 ` [PATCH 3/6] bootwrapper: Add support for cuboot platforms Scott Wood
2007-03-23 5:25 ` David Gibson
2007-03-22 19:49 ` [PATCH 4/6] bootwrapper: Add CONFIG_DEVICE_TREE Scott Wood
2007-03-22 19:49 ` [PATCH 5/6] bootwrapper: Add a cuImage target Scott Wood
2007-03-23 5:40 ` David Gibson
2007-03-23 15:18 ` Scott Wood
2007-03-23 23:39 ` David Gibson [this message]
2007-03-22 19:49 ` [PATCH 6/6] bootwrapper: cuboot for 83xx Scott Wood
2007-03-23 5:54 ` David Gibson
2007-03-23 15:30 ` Scott Wood
2007-03-23 23:37 ` David Gibson
2007-03-26 15:53 ` Scott Wood
2007-04-04 2:06 ` Mark A. Greer
2007-04-04 6:38 ` David Gibson
2007-04-04 16:01 ` 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=20070323233927.GD4459@localhost.localdomain \
--to=david@gibson.dropbear.id.au \
--cc=linuxppc-dev@ozlabs.org \
--cc=scottwood@freescale.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).