Hi, Following on the special handling of nodes called memory@0, I went to have a look at the various platforms that do not actually declare a device_type = "memory" for their "memory" nodes. Firstly, we currently have 162(ish, I did a sloppy grep) such .dts{i} files in the kernel tree. Secondly, the only reason these platforms could ever have worked is because they include .dtsi files that define a memory node with a type explicitly set. Since this node already exists, its contents get overridden, but the type tag remains. Of course, this only happens with nodes called explicitly "memory" - but it happens regardless of what other things they contain. In the ARM tree, most of these seem to stem from the inclusion of skeleton.dtsi. I don't really know what could/should be done about this, but it does not feel optimal. / Leif -- 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