title: How to use custom device tree source correctly in buildroot?
body: <p>I made a copy of the dts from <code>&lt;linux&gt;/board/arch/arm/boot/dts/imx28-evk.dts</code> for using with my custom board. My custom device-tree is named <code>imx28-custom.dts</code> and is pointed in the <em>Out of tree custom DTS</em> menu entry (<code>BR2_LINUX_KERNEL_CUSTOM_DTS_PATH</code>) in the Buildroot config.</p>
  <p>However u-boot is configured to use the existing MX28 board config. After building a kernel I have <code>imx28-custom.dtb</code> and <code>zImage</code> in the <code>&lt;buildroot&gt;/output/images</code> folder.</p>
  <p>When the system boots, u-boot tells that <code>imx28-evk.dtb</code> is not found. Why was <code>imx28-custom.dtb</code> built but is not found by u-boot? Why u-boot doesn't find its own device-tree (<code>imx28-evk.dtb</code>) for itself and my custom device-tree for the kernel? I assumed that <code>BR2_LINUX_KERNEL_CUSTOM_DTS_PATH</code> relates only to the kernel. How can my custom device-tree be passed to the kernel if u-boot tries to use its own <code>imx28-evk.dtb</code> for this?</p>