On Wed, Dec 30, 2009 at 4:39 PM, Peter Tyser <ptyser@xxxxxxxxxxx> wrote: > Hi Grant, > I put U-Boot ML on CC. Thinking further, I do actually have another concern, at least with regard to the way the current patch set implements things. Is it expected or even "recommended" that fit images will *always* contain a .dtb image? The current patch only handles the case of a .dtb embedded inside the fit image. Personally, I don't get any benefit out of the new image format, so I haven't spent any time looking at it. However, I'm concerned about the drift back towards a different image per target when the move over the last 4 years has been towards multiplatform kernel images. I certainly don't want to encourage embedding the device tree blob into the kernel image, and I'm not very interested in merging code to do that into the kernel tree. If someone really needs to do that for their particular target, it is certainly easy enough for them to weld in the .dtb after the fact before transferring the image to the target, but I want that mode to be the exception, not the rule. g. -- Grant Likely, B.Sc., P.Eng. Secret Lab Technologies Ltd. -- To unsubscribe from this list: send the line "unsubscribe linux-kbuild" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html