On Thu, Sep 21, 2023 at 1:45 PM Simon Glass sjg@chromium.org wrote:
Binman[1] is a tool for creating firmware images. It allows you to combine various binaries and place them in an output file.
Binman uses a DT schema to describe an image, in enough detail that it can be automatically built from component parts, disassembled, replaced, listed, etc.
Images are typically stored in flash, which is why this binding is targeted at mtd. Previous discussion is at [2] [3].
[1] https://u-boot.readthedocs.io/en/stable/develop/package/binman.html [2] https://lore.kernel.org/u-boot/20230821180220.2724080-3-sjg@chromium.org/ [3] https://www.spinics.net/lists/devicetree/msg626149.html
You missed:
https://github.com/devicetree-org/dt-schema/pull/110
where I said: We certainly shouldn't duplicate the existing partitions bindings. What's missing from them (I assume we're mostly talking about "fixed-partitions" which has been around forever I think (before me))?
To repeat, unless there is some reason binman partitions conflict with fixed-partitions, you need to start there and extend it. From what's posted here, it neither conflicts nor needs extending.
I did a bit more research. "fixed-partitions" as a compatible has "only" been around since 2015. Prior to that, it was implicit with just partition nodes with addresses (i.e. reg) and that dates back to 2007. Looks like u-boot only supports the newer form and since 2021.
Rob