Re: [RFC v2 1/2] libfdt: add fdt_alignprop

Simon Glass writes: > Can you use an external FIT? Maybe. I couldn't make that work in a quick test, but that is probably just me doing something wrong. But there are other workarounds for this specific device, yes. Appending the DTB to the kernel image is verified to work. So it is possible

Re: [RFC v2 0/2] Prevent alignment issues with "in place" FIT configurations

x: re-sign if nops were added MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Signed-off-by: Bjørn Mork --- tools/fit_image.c | 14 ++ 1 file changed, 14 insertions(+) diff --git a/tools/fit_image.c b/tools/fit_image.c index 2e215ca2199d..c29e209

[RFC v2 2/2] mkimage: Align fdt images in FIT to 8 bytes

ese problems, at the maximum price of 4 bytes per fdt. Signed-off-by: Bjørn Mork --- tools/fit_image.c | 39 +++ 1 file changed, 39 insertions(+) diff --git a/tools/fit_image.c b/tools/fit_image.c index 923a9755b709..1e060784895d 100644 --- a/tools/fit

[RFC v2 1/2] libfdt: add fdt_alignprop

, i.e. the embedded fdt, happens to match the 8-byte boundary required by the devicetree spec. Adding the ability to align property data allows U-Boot tools to reliably create FIT images for such use. Other use cases are currently not known, but anticipated. Signed-off-by: Bjørn Mork --- s

[RFC v2 0/2] Prevent alignment issues with "in place" FIT configurations

I'v posted a similar request to the devicetree-compiler list with those changes. The libfdt patch is included here for convenience. The expected impact for U-Boot is only the tools/fit_image.c patch. Bjørn Changes v2: - actually use the new fdt_alignprop() instead of an earlier PoC hack