From: Quentin Schulz <quentin.schulz@cherry.de>
To: adrian.freihofer@siemens.com, docs@lists.yoctoproject.org
Cc: kavinaya@qti.qualcomm.com
Subject: Re: [docs] [PATCH] ref-manual/variables.rst: cover FIT_LINUX_BIN variable
Date: Tue, 21 Oct 2025 10:49:48 +0200 [thread overview]
Message-ID: <7d15f2ff-bc28-4ae2-b797-890f1473dcef@cherry.de> (raw)
In-Reply-To: <20251019164740.3795019-1-adrian.freihofer@siemens.com>
Hi Adrian,
On 10/19/25 6:47 PM, Adrian Freihofer via lists.yoctoproject.org wrote:
> From: Adrian Freihofer <adrian.freihofer@siemens.com>
>
> Document the FIT_LINUX_BIN variable used in the fit-image class to specify
> the kernel binary name included in the FIT image.
>
> Signed-off-by: Adrian Freihofer <adrian.freihofer@siemens.com>
> ---
> documentation/ref-manual/variables.rst | 12 ++++++++++++
> 1 file changed, 12 insertions(+)
>
> diff --git a/documentation/ref-manual/variables.rst b/documentation/ref-manual/variables.rst
> index 591c03028ce..8a10dfc54e6 100644
> --- a/documentation/ref-manual/variables.rst
> +++ b/documentation/ref-manual/variables.rst
> @@ -3430,6 +3430,18 @@ system and gives an overview of their function and contents.
> The default value is set to "x509" by the
> :ref:`ref-classes-kernel-fit-image` class.
>
> + :term:`FIT_LINUX_BIN`
> + This variable is used in the :ref:`ref-classes-kernel-fit-image` class to
> + specify the name of the Linux kernel binary which gets included in the
> + FIT image.
That is not true.
> + The default value is set to "linux.bin".
> +
You have two choices. The empty string or anything not empty (including
the default "linux.bin"). The value of the non empty string does not
matter at all.
The wording here implies something that does not happen. It does not
represent the name of the Linux kernel binary which gets included in the
FIT image, it is merely sort of a boolean to decide whether to include
linux.bin binary in the kernel FIT image.
linux.bin is generated by uboot_prep_kimage() in
meta/classes-recipe/kernel-uboot.bbclass which is called in
kernel_do_deploy:append() in
meta/classes-recipe/kernel-fit-extra-artifacts.bbclass which is
inherited whenever it is present in KERNEL_CLASSES variable. Its
compression is stored in linux_comp file which is also read whenever
FIT_LINUX_BIN is set. So changing FIT_LINUX_BIN logic would require a
change for the compression field in the FIT as well.
Cheers,
Quentin
prev parent reply other threads:[~2025-10-21 8:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-19 16:47 [PATCH] ref-manual/variables.rst: cover FIT_LINUX_BIN variable AdrianF
2025-10-20 6:47 ` [docs] " Antonin Godard
2025-10-20 21:14 ` Freihofer, Adrian
2025-10-21 8:49 ` Quentin Schulz [this message]
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=7d15f2ff-bc28-4ae2-b797-890f1473dcef@cherry.de \
--to=quentin.schulz@cherry.de \
--cc=adrian.freihofer@siemens.com \
--cc=docs@lists.yoctoproject.org \
--cc=kavinaya@qti.qualcomm.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