On 2023-09-21 21:45 +03:00, Simon Glass 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
Signed-off-by: Simon Glass sjg@chromium.org
.../bindings/mtd/partitions/binman.yaml | 50 +++++++++++++++ .../bindings/mtd/partitions/binman/entry.yaml | 61 +++++++++++++++++++ .../bindings/mtd/partitions/partitions.yaml | 1 + MAINTAINERS | 5 ++ 4 files changed, 117 insertions(+) create mode 100644 Documentation/devicetree/bindings/mtd/partitions/binman.yaml create mode 100644 Documentation/devicetree/bindings/mtd/partitions/binman/entry.yaml
This doesn't match the schema in [2], but seems more like v1 of that. Is that intentional?