Hello Stephen, > >> > >> Adding something to obj-, which presumably isn't used at all, seems very > >> odd. > > > > Why do we even need arch/arm/cpu/armv7/tegra124/Makefile ? I assume we > > need the config.mk because we can't stick CONFIG_ARCH_DEVICE_TREE into > > the config header? > > At least with the current build system, if I delete it, the build fails: > > > + make > > BUILD_DIR=/home/swarren/shared/git_wa/tegra-uboot-flasher/_build/venice2/u-boot > > -s -j9 > > /home/swarren/shared/git_wa/tegra-uboot-flasher/u-boot/scripts/Makefile.build:11: > > Makefile: No such file or directory > > make[1]: *** No rule to make target `Makefile'. Stop. > > make: *** > > [/home/swarren/shared/git_wa/tegra-uboot-flasher/_build/venice2/u-boot/arch/arm/cpu/armv7/tegra124/built-in.o] > > Error 2
Yes, we can't delete the Makefile. (This is the same as before Kbuild.) Venice2 board specify SoC name, tegra124 in boards.cfg. If $(SOC) is not empty, the build system will descend into the SoC directory, and Makefile always must be there. I understand the special situation for Tegra, which has a different CPU for SPL. I guess you want to build under arch/arm/cpu/arm720t/tegra124/ for SPL, whereas there is nothing to build under arch/arm/cpu/armv7/tegra124/. Best Regards Masahiro Yamada _______________________________________________ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
