On Wed, Mar 18, 2015 at 10:29 PM, Frank Rowand <frowand.list@xxxxxxxxx> wrote: > Rob, > > Can this be added to the next trees to get some test exposure before submitting > to Linus? No. I've yet to see anyone think this is a good idea. > There is currently no way to tie a device tree blob (DTB) back to the source > and environment used to create it. Add this information, including a DTB > version number, which is somewhat analogous to the Linux kernel version number. > > The DTB version number is independent of the kernel version number, and is > incremented for each make of one or more DTBs. > > The DTB information is placed in node /chosen/dtb-info. The data for this > node will be automatically generated by the .dtb make system for any .dts > that includes arch/arm/boot/dts/skeleton.dtsi, either directly or indirectly. > This means that architectures other than arm will not receive this feature. > This can be added to other architectures by modifying their skeleton.dtsi. > > There are 70 of the 557 arm .dts files that do not include skeleton.dtsi. > Thus the .dtb files created for these systems will not have the > /chosen/dtb-info node: Actually, we really want to get rid of skeleton.dtsi. At least the memory node because it obscures whether the memory node is correct or not. Then if there is no memory node, there is not much point to it. Rob -- 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
