[U-Boot] [PATCH] integrator: convert to new build system

Linus Walleij linus.walleij at linaro.org
Wed Jul 20 09:56:32 CEST 2011


On Tue, Jul 19, 2011 at 10:04 PM, Wolfgang Denk <wd at denx.de> wrote:

> [Me]
>>  include/configs/integratorap.h              |    3 +
>>  include/configs/integratorap_cm720t.h       |    1 +
>>  include/configs/integratorap_cm920t.h       |    1 +
>>  include/configs/integratorap_cm926ejs.h     |    1 +
>>  include/configs/integratorap_cm946es.h      |    1 +
>>  include/configs/integratorcp.h              |    2 +
>>  include/configs/integratorcp_cm1136.h       |    1 +
>>  include/configs/integratorcp_cm920t.h       |    1 +
>>  include/configs/integratorcp_cm926ejs.h     |    1 +
>>  include/configs/integratorcp_cm946es.h      |    1 +
>
> It appears that all the new board config files just include
> integrator[ac]p.h, without any additional stuff.

Yes, that's how it works...

> Would it not make
> sense to omit these file alltogether then, and let the entries in
> boards.cfg point to the generic files integratorap.h resp.
> integratorcp.h instead?

This row in the global Makefile is the reason:

sinclude $(obj).boards.depend
$(obj).boards.depend:   boards.cfg
        awk '(NF && $$1 !~ /^#/) { print $$1 ": " $$1 "_config;
$$(MAKE)" }' $< > $@

It requires one *_config per board variant.

The boards are just two variants, but the CPU column differs for all of
them, depending on what CPU Module (CM) you plug into the board.

So I define these different boards just to get the right value of CPU into
$(obj)/include/config.mk

I haven't quite figured out how that file is generated, but to avoid any
more configure options being passed in it seemed like the only way
forward without revamping the build system.

Hacking Makefile to support several boards using the same *_config
seems pretty daunting, but if this is what you want I can try.

Any hints?

Yours,
Linus Walleij


More information about the U-Boot mailing list