Hello Tony, As discussed in [0], there's a regression when booting a kernel with a DTB that doesn't have a pre-existing chosen node. This is usually not an issue for most boards since u-boot creates an empty chosen node if isn't present in the DTB. But it can be an issue for others bootloaders as Pali pointed out with the N9/900/950 phones and the Nokia Loader (NoLo). This patch series add chosen nodes in the top level DTSI for all OMAP SoCs. [0]: http://www.mail-archive.com/linux-kernel@xxxxxxxxxxxxxxx/msg1294379.html Best regards, Javier Javier Martinez Canillas (9): ARM: dts: omap2: Add an empty chosen node to top level DTSI ARM: dts: omap3: Add an empty chosen node to top level DTSI ARM: dts: omap4: Add an empty chosen node to top level DTSI ARM: dts: omap5: Add an empty chosen node to top level DTSI ARM: dts: am33xx: Add an empty chosen node to top level DTSI ARM: dts: am4372: Add an empty chosen node to top level DTSI ARM: dts: dm814x: Add an empty chosen node to top level DTSI ARM: dts: dm816x: Add an empty chosen node to top level DTSI ARM: dts: dra7: Add an empty chosen node to top level DTSI arch/arm/boot/dts/am33xx.dtsi | 1 + arch/arm/boot/dts/am4372.dtsi | 1 + arch/arm/boot/dts/dm814x.dtsi | 1 + arch/arm/boot/dts/dm816x.dtsi | 1 + arch/arm/boot/dts/dra7.dtsi | 1 + arch/arm/boot/dts/omap2.dtsi | 1 + arch/arm/boot/dts/omap3.dtsi | 1 + arch/arm/boot/dts/omap4.dtsi | 1 + arch/arm/boot/dts/omap5.dtsi | 1 + 9 files changed, 9 insertions(+) -- 2.7.4 -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
