Hi, Please copy me at linux@xxxxxxxxxxxxxxx not rmk@xxxxxxxxxxxxxxx - this entire series has ended up in my spam folder. On Tue, Apr 17, 2018 at 12:10:02PM +0300, Tero Kristo wrote: > Hi, > > This series is an attempt to start discussion on the DT overlay build time > support. Basically, one can build DT overlays directly from kernel tree, > and also build FIT images that contain the kernel + devicetree blobs > required for specific configuration that can be booted directly with > u-boot. No runtime support for overlay switching is touched by this > series. > > The main controversy with this series is most likely where the DT overlay > files should be stored at. Should they still reside with the kernel > tree or someplace else? Also, the FIT image support is probably > controversial, should it be part of the kernel build system like shown > here, or should it be separate? The zImage dependency is pretty annoying > so maybe it should be done somewhere else. Please, no, do not add any further build targets for special boot loader formats. We already deprecate the "uImage" format when building multi- platform kernels. The problem is that we either need to pass in parameters like the load address and dtb path to include in the image, or we need to add to the kernel build system the load addresses for every platform, and generate hundreds of images eating up lots of disk space, and adding to the kernel build time. When we switched to dtb and multi-platform support, we decided that it was much better that such bootloader specific stuff be external to the kernel tree. -- Russell King -- 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
