From: Roland Hieber <rhi@pengutronix.de>
To: ptxdist@pengutronix.de
Cc: Roland Hieber <rhi@pengutronix.de>
Subject: [ptxdist] [PATCH v3 3/3] doc: ref_make_macros: document world/image-fit macro
Date: Tue, 12 Sep 2023 18:57:59 +0200 [thread overview]
Message-ID: <20230912165759.3492269-3-rhi@pengutronix.de> (raw)
In-Reply-To: <20230912165759.3492269-1-rhi@pengutronix.de>
Signed-off-by: Roland Hieber <rhi@pengutronix.de>
---
PATCH v3: no change
PATCH v2: no change
PATCH v1: https://lore.ptxdist.org/ptxdist/20230822121234.2040303-3-rhi@pengutronix.de
---
doc/ref_make_macros.rst | 38 ++++++++++++++++++++++++++++++++++++++
1 file changed, 38 insertions(+)
diff --git a/doc/ref_make_macros.rst b/doc/ref_make_macros.rst
index b8cfe9eff644..fe300c45757a 100644
--- a/doc/ref_make_macros.rst
+++ b/doc/ref_make_macros.rst
@@ -175,6 +175,44 @@ omitted.
``ptx/image-install-link`` creates a symlink in the image directory.
+.. _world_image_fit:
+
+world/image-fit
+~~~~~~~~~~~~~~~
+
+.. code-block:: none
+
+ @$(call world/image-fit, <PKG>)
+
+Build a FIT image containing a kernel, optionally an initial ramdisk, and one or
+multiple device trees. For each device tree, a configuration node is generated.
+
+.. note:: You can generate a template for a new FIT image recipe by
+ calling ``ptxdist newpackage image-fit``.
+
+The following variables are respected:
+
+``<PKG>_IMAGE``
+ The output file, usually something like ``$(IMAGEDIR)/pkg.fit``.
+
+``<PKG>_KERNEL``
+ The kernel image to package into the FIT image.
+
+``<PKG>_DTB``
+ One or more device trees that should be included in the FIT image.
+
+``<PKG>_INITRAMFS``
+ If the FIT image should contain an initial ramdisk, this variable determines
+ the initrd file name that is included. Otherwise it can be left empty.
+
+``<PKG>_SIGN_ROLE``
+ If the FIT image should be signed, this variable determines the role name
+ used for the signature. It is passed to :ref:`cs_get_uri`.
+
+``<PKG>_KEY_NAME_HINT``
+ If the FIT image should be signed, this variable determines the
+ *key-name-hint* property of the signature node.
+
.. _install_copy:
install_copy
--
2.39.2
next prev parent reply other threads:[~2023-09-12 16:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-12 16:57 [ptxdist] [PATCH v3 1/3] kernel: add make target for the installed device trees Roland Hieber
2023-09-12 16:57 ` [ptxdist] [PATCH v3 2/3] templates: add template for custom FIT images Roland Hieber
2023-09-24 5:44 ` [ptxdist] [APPLIED] " Michael Olbrich
2023-09-12 16:57 ` Roland Hieber [this message]
2023-09-24 5:44 ` [ptxdist] [APPLIED] doc: ref_make_macros: document world/image-fit macro Michael Olbrich
2023-09-24 5:44 ` [ptxdist] [APPLIED] kernel: add make target for the installed device trees Michael Olbrich
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=20230912165759.3492269-3-rhi@pengutronix.de \
--to=rhi@pengutronix.de \
--cc=ptxdist@pengutronix.de \
/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