Dear "Wolfgang Denk"

OK, just two questions.

All the boards I am using use the same link script, shall I copy it to its specific directory? Do you really want this? It is not better to do it like the MODE B (cp common_script to board dir)?

I want to create two different targets: ml507 and ml507_flash. Could you write an example of how to do this without writing the TEXT_BASE in the Makefile? I did it in this way because I didn't found any other method in the main Makefile

Thank you very much for your help

Regards

On Fri, Aug 29, 2008 at 18:24, Wolfgang Denk wd@denx.de wrote:

Dear "Ricardo Ribalda Delgado",

In message aa76a2be0808291417i462624fdya22c97d12f74db68@mail.gmail.com you wrote:

...

Before this "unification" patch I send another path that did treat the avnet board as a new board (a lot of code replication). This is what I call the old way.

Let me be more clear. What do we want:

MODE A

ml507_config: unconfig BOARD_DIR=$(obj)board/xilinx/ml507 \ TEXT_BASE=0x3000000 \ LINK_SCRIPT=$(obj)board/xilinx/ppc440-generic/u-boot-ram.lds \ CONFIG_SCRIPT="ml507 ppc ppc4xx ml507 xilinx" \ $(MAKE) xilinx_ppc440

BOARD_DIR, TEXT_BASE, LINK_SCRIPT and CONFIG_SCRIPT have no place in the top level Makefile. Please move this to board specific directories.

The normal entry for a board should consist of not more than

<name>_config: unconfig @$(MKCONFIG) <name> ppc4xx xilinx <name>

or similar.

Best regards,

Wolfgang Denk

-- DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@denx.de "Most people would like to be delivered from temptation but would like it to keep in touch." - Robert Orben