From: Alper Nebi Yasak <alpernebiyasak@gmail.com>
To: Simon Glass <sjg@chromium.org>
Cc: "U-Boot Mailing List" <u-boot@lists.denx.de>,
linux-mtd@lists.infradead.org, "Tom Rini" <trini@konsulko.com>,
"Rob Herring" <robh@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"Dhruva Gole" <d-gole@ti.com>,
"Krzysztof Kozlowski" <krzysztof.kozlowski+dt@linaro.org>,
"Miquel Raynal" <miquel.raynal@bootlin.com>,
"Rafał Miłecki" <rafal@milecki.pl>,
"Richard Weinberger" <richard@nod.at>,
"Rob Herring" <robh+dt@kernel.org>,
"Vignesh Raghavendra" <vigneshr@ti.com>,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH] dt-bindings: mtd: Add a schema for binman
Date: Fri, 22 Sep 2023 16:56:55 +0300 [thread overview]
Message-ID: <e045afaa-bc38-4fed-966e-a034e106c86c@gmail.com> (raw)
In-Reply-To: <20230921124459.1.I91ddcfacf9b234af5cc3eabea4b62edb31153317@changeid>
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?
next prev parent reply other threads:[~2023-09-22 13:57 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-21 18:45 [PATCH] dt-bindings: mtd: Add a schema for binman Simon Glass
2023-09-22 4:21 ` Rob Herring
2023-09-22 7:01 ` Krzysztof Kozlowski
2023-09-22 15:26 ` Simon Glass
2023-09-22 13:56 ` Alper Nebi Yasak [this message]
2023-09-22 15:09 ` Simon Glass
2023-09-22 16:00 ` Rob Herring
2023-09-22 17:01 ` Simon Glass
2023-09-22 17:46 ` Rob Herring
2023-09-22 18:12 ` Simon Glass
2023-09-22 19:43 ` Rob Herring
2023-09-22 19:51 ` Simon Glass
2023-09-25 7:21 ` Miquel Raynal
2023-09-25 12:33 ` Simon Glass
2023-09-25 14:47 ` Miquel Raynal
2023-09-25 14:53 ` Simon Glass
2023-09-25 15:24 ` Miquel Raynal
2023-09-25 16:25 ` Simon Glass
2023-09-25 18:49 ` Rob Herring
2023-09-25 22:25 ` Simon Glass
2023-09-26 7:48 ` Miquel Raynal
2023-09-26 17:29 ` Rob Herring
2023-09-27 16:43 ` Simon Glass
2023-09-28 15:20 ` Simon Glass
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=e045afaa-bc38-4fed-966e-a034e106c86c@gmail.com \
--to=alpernebiyasak@gmail.com \
--cc=conor+dt@kernel.org \
--cc=d-gole@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=miquel.raynal@bootlin.com \
--cc=rafal@milecki.pl \
--cc=richard@nod.at \
--cc=robh+dt@kernel.org \
--cc=robh@kernel.org \
--cc=sjg@chromium.org \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
--cc=vigneshr@ti.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).