Thread (7 messages) flat view 7 messages, 4 authors, 2007-01-25

Re: [PATCH 01/18] Include autoconf.h from the bootwrapper.

From: Scott Wood <hidden>
Date: 2007-01-25 17:39:42

On Thu, Jan 25, 2007 at 01:40:59PM +1100, Paul Mackerras wrote:
Kumar Gala writes:
quoted
I think the problem is how to resolve the variations of the u-boot/ 
ppcboot bd_t that changes from board to board and based on config.
The wrapper should be able to build bootable images for any of the
boards, that is, for any given bd_t variant, there should be a flag to
wrapper that tells it to build an image that understands that variant.

It's reasonable for arch/powerpc/boot/Makefile to pass different flags
to wrapper depending on the kernel config.  I don't want wrapper
itself, or anything it uses, to be config-dependent.
So basically, there'd be several lines in the arch/powerpc/boot/Makefile
like this?

cflags-$(CONFIG_6xx) += -DCONFIG_6xx
cflags-$(CONFIG_8xx) += -DCONFIG_8xx
cflags-$(CONFIG_E500) += -DCONFIG_E500
BOOTCFLAGS += $(cflags-y)

I don't really see the point (a simple grep will show you all the config
dependencies in the bootwrapper, to verify that it's only platform stuff
and not actual options), but I can do it that way if you really want. 
One way or another, the information has to be there, and it has to be
compile-time or else the bd_info struct layout will be wrong.

-Scott
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help