
25 Nov
2010
25 Nov
'10
6:19 p.m.
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 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?
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
The world is no nursery. - Sigmund Freud