On 01/23/2018 10:17 PM, Frank Rowand wrote: [...] > My knowledge of bootloader use of the FDT is nearly non-existent, so > I'm on thin ice here. But I am guessing that a lot of bootloader > processing of FDT data could be removed if the kernel would unflatten > a chained FDT and overlay FDT(s). > > Comments from the bootloader folks on this topic would be much > appreciated. U-Boot, when using DT as a hardware-description (rather than just passing it to Linux) usually operates on the FDT, unless explicitly configured to unflatten the tree. That later option is not enabled by default. The reason for that is so that the DT can be accessed very early on, at which point there may not be any other memory available than a very limited stack and the FDT blob can still be located in some read-only memory. -- Best regards, Marek Vasut -- To unsubscribe from this list: send the line "unsubscribe devicetree-compiler" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
