On 2/26/19 7:36 PM, Masahiro Yamada wrote:
On Wed, Feb 27, 2019 at 11:17 AM Masahiro Yamada
<yamada.masah...@socionext.com> wrote:
On Wed, Feb 27, 2019 at 4:21 AM Stephen Warren <swar...@wwwdotorg.org> wrote:
From: Stephen Warren <swar...@nvidia.com>
Without this, the arch-dtbs target only gets evaluated when building
U-Boot the first time, not when re-building (incrementally building)
U-Boot. Thus incremental builds ignore changes to DTB files.
Really?
I tested "touch DT, then incremental build",
and it correctly re-compiled device tree.
I attached the log of the following build sequence:
[1] make jetson-tk1_defconfig
[2] make CROSS_COMPILE=arm-linux-gnueabihf-
[3] touch arch/arm/dts/tegra124-jetson-tk1.dts
[4] make CROSS_COMPILE=arm-linux-gnueabihf-
Hmm, OK. Understood.
The jetson DT was recompiled,
but the other tegra DT files were not.
Yes, perhaps I should have mentioned that I found this issue when
building sandbox. Sandbox's default DTB of sandbox.dtb does get
recompiled as expected, but test.dtb (used by the test/py/ test system)
does not, for incremental builds.
_______________________________________________
U-Boot mailing list
U-Boot@lists.denx.de
https://lists.denx.de/listinfo/u-boot
