On Tue, Feb 12, 2013 at 01:19:18PM -0700, Stephen Warren wrote: > On 02/12/2013 03:41 AM, Thierry Reding wrote: > ... > > So it turned out that I need to touch U-Boot anyway, so I decided > > to give this a spin. I noticed that overriding > > CONFIG_ARCH_DEVICE_TREE from the board configuration file doesn't > > work currently. What happens is that the autoconf.mk (which is > > derived from the board configuration) is included before the CPU > > config.mk which sets CONFIG_ARCH_DEVICE_TREE to tegra20 (or > > tegra30, tegra114). I came up with the attached patch to set the > > variable if not set previously (by the board configuration file). > > > > Feel free to squash that in your patch series if you deem it a > > proper solution. I can also provide a proper separate patch if you > > prefer. > > > diff --git a/arch/arm/cpu/armv7/tegra114/config.mk > > b/arch/arm/cpu/armv7/tegra114/config.mk > > > -CONFIG_ARCH_DEVICE_TREE := tegra114 +CONFIG_ARCH_DEVICE_TREE ?= > > tegra114 > > That looks very odd. What value is CONFIG_ARCH_DEVICE_TREE before that > assignment, and why exactly is it wrong?
Tom's patches add a
#define CONFIG_ARCH_DEVICE_TREE tegra20-tamonten
to the configuration files of Tamonten-derived boards so that the proper
DTSI is picked up. However, that line causes the make variable to be
defined in autoconf.mk, which is included before the CPU config.mk, so
if the config.mk has
CONFIG_ARCH_DEVICE_TREE := tegra20
it will overwrite the value set by autoconf.mk.
Thierry
pgp_d4uTJzj8J.pgp
Description: PGP signature
_______________________________________________ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
