On 11/05/2012 01:40 PM, Grant Likely wrote: > As promised, here is my early draft to try and capture what device > tree overlays need to do and how to get there. Comments and > suggestions greatly appreciated. Here's one other requirement I'd like that I don't think I saw explicitly mentioned in your document: Assuming a base file board.dts and a child board file child.dts, the compiled file child.dtb should be usable with a modified board.dtb assuming it exports the same set of attachment-points (hashed phandles, socket objects, whatever). This allows bug-fixes etc. to board.dts without forcing every child.dts to be recompiled. If the attachment points is hashed node names or node content from board.dts, I'm not sure how this is possible? I suppose this is implicit if child.dtb can be used with either board-a.dtb and board-b.dtb though. -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
