[PATCH 19/19] bootwrapper: compatibility layer for old U-Boots (a.k.a. cuImage, cuboot)

Scott Wood scottwood at freescale.com
Tue Feb 13 03:52:59 EST 2007

David Gibson wrote:
> On Fri, Feb 09, 2007 at 11:11:29AM -0600, Scott Wood wrote:
>>They come from platform files such as cuboot-83xx.c, not (directly) from 
>>the kernel config.
> /me looks again...
> .c files containing only #defines?  My brain hurts.

So does mine.  It wasn't my idea...

> Better to pass these in as -D flags from the gcc invocation within the
> wrapper script, depending on the given platform (for the platform .o
> *only*). 

I was explicitly told by Paul that it had to be link-time, not compile-time.

See "http://ozlabs.org/pipermail/linuxppc-dev/2007-January/030532.html".

Unless you're saying that the "wrapper" script should do the compilation 
itself, rather than just linking as it currently does...  in which case 
I'd really like to know what real benefit we're getting out of all this 

> Oh, and please don't call them CONFIG_* or everyone will
> assume, like me, that they come from the kernel's overall config.h.

Well, they are related, and I'd have to make ppcboot.h diverge even more 
from u-boot's version to call it something else.

But I can rename it TARGET_* or something if it'd make y'all happier.


More information about the Linuxppc-dev mailing list