u-boot.lists.denx.de archive mirror
 help / color / mirror / Atom feed
From: Simon Glass <sjg@chromium.org>
To: U-Boot Mailing List <u-boot@lists.denx.de>
Cc: Xavier Drudis Ferran <xdrudis@tinet.cat>,
	Quentin Schulz <quentin.schulz@theobroma-systems.com>,
	Alper Nebi Yasak <alpernebiyasak@gmail.com>,
	Simon Glass <sjg@chromium.org>
Subject: [PATCH 1/2] binman: Mention split-elf in the main docs
Date: Thu, 18 Aug 2022 02:16:45 -0600	[thread overview]
Message-ID: <20220818081647.210263-1-sjg@chromium.org> (raw)

Since we are talking about ATF, add mention of this new feature too.

Signed-off-by: Simon Glass <sjg@chromium.org>
---

 tools/binman/binman.rst | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/tools/binman/binman.rst b/tools/binman/binman.rst
index 6e1fd3476f1..f85d13b700a 100644
--- a/tools/binman/binman.rst
+++ b/tools/binman/binman.rst
@@ -236,6 +236,10 @@ variable. Within binman, this EntryArg is picked up by the `Entry_atf_bl31`
 etype. An EntryArg is simply an argument to the entry. The `atf-bl31-path`
 name is documented in :ref:`etype_atf_bl31`.
 
+Taking this a little further, when binman is used to create a FIT, it supports
+using an ELF file, e.g. `bl31.elf` and splitting it into separate pieces (with
+`fit,operation = "split-elf"`), each with its own load address.
+
 
 Invoking binman outside U-Boot
 ------------------------------
-- 
2.37.1.595.g718a3a8f04-goog


             reply	other threads:[~2022-08-18  8:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-18  8:16 Simon Glass [this message]
2022-08-18  8:16 ` [PATCH 2/2] binman: Document how to handle dependent images Simon Glass
2022-08-27  1:59 ` Simon Glass
2022-08-27  1:59 ` [PATCH 1/2] binman: Mention split-elf in the main docs 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=20220818081647.210263-1-sjg@chromium.org \
    --to=sjg@chromium.org \
    --cc=alpernebiyasak@gmail.com \
    --cc=quentin.schulz@theobroma-systems.com \
    --cc=u-boot@lists.denx.de \
    --cc=xdrudis@tinet.cat \
    /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).