On Thu, 2010-11-25 at 10:19 -0700, Wolfgang Denk wrote:
Dear Haiying Wang,
In message 1290702018.2007.4.camel@haiying-laptop you wrote:
- If CONFIG_SYS_LDCONFIG is not set, and the system is booting
from
NAND (CONFIG_NAND_U_BOOT is set), then a board specific linker script board/$(BOARDDIR)/u-boot-nand.lds gets use.
u-boot-nand.lds is not in board/$(BOARDDIR) for 85xx at least, it is
in
$(SRCTREE)/$(CPUDIR)/
This is not correct - situation before applying my patches:
-> find * -name u-boot-nand.lds arch/powerpc/cpu/mpc85xx/u-boot-nand.lds
so your patch for arch/powerpc/config.mk will not get u-boot-nand.lds for mpc85xx boards, only for the boards below. Then 85xx boards still need to get the lds from board/$(BOARDIR)/config.mk. Is that what you want?
board/amcc/acadia/u-boot-nand.lds board/amcc/bamboo/u-boot-nand.lds board/amcc/canyonlands/u-boot-nand.lds board/amcc/kilauea/u-boot-nand.lds board/amcc/sequoia/u-boot-nand.lds board/esd/pmc440/u-boot-nand.lds board/samsung/smdk6400/u-boot-nand.lds
- If we are not booting from NAND, we test if a processor specific linker script arch/powerpc/cpu/$(CPU)/u-boot.lds exists; if so
we
use that.
should we use $(CPUDIR) instead of arch/powerpc/cpu/$(CPU)?
I'm not sure if CPUDIR is defined at that time. Did you try it out?
CPUDIR is defined in config.mk, I tried it for 85xx/p1 boards and it worked.
Haiying