U-Boot builds devicetree binaries from its source tree. As part of the Kconfig conversion, the Makefiles were updated to align with how this is done in Linux: a single target for each SoC is used to build all the .dtb files for that SoC.
Since then, the Makefiles have devolved in some cases, resulting in lots of target-specific build rules. Also Linux has moved to using subdirectories for each vendor. Recent work aims to allow U-Boot to directly use devicetree files from Linux. This would be easier if the directory structure were the same. Another recent discussion involved dropping the build rules altogether. This series makes a start at cleaning up some of the build rules, to reduce the amount of code and make it easier to add new boards for the same SoC. One issue is that the ARCH_xxx Kconfig options between U-Boot and Linux are not always the same. Given the large number of SoCs and boards supported by U-Boot, it would be useful to align these where possible. Simon Glass (9): microblaze: dts: Use the normal build rule nios2: dts: Use the normal build rule arm: at91: dts: Start an SoC-specific build rule arm: at91: dts: Complete conversion of dts build rules arm: at91: dts: Sort at91 rules arm: samsung: dts: Convert to SoC-specific build rules arm: ti: dts: Convert OMAP to SoC-specific build rules arm: qualcomm: dts: Convert to SoC-specific build rules arm: vexpress: dts: Convert to SoC-specific build rules arch/arm/dts/Makefile | 174 ++++++++++++++--------------------- arch/microblaze/dts/Makefile | 2 +- arch/nios2/dts/Makefile | 2 +- 3 files changed, 73 insertions(+), 105 deletions(-) -- 2.34.1
