From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: nora.schiffer@ew.tq-group.com, openembedded-core@lists.openembedded.org
Cc: oss@ew.tq-group.com
Subject: Re: [OE-core] [PATCH v2 1/3] kernel-uboot: move FIT_KERNEL_COMP_ALG to image-fitimage.conf
Date: Thu, 30 Jul 2026 11:43:48 +0100 [thread overview]
Message-ID: <f0ab7f4d7d6c72feb2b1b8122a4434db98799370.camel@linuxfoundation.org> (raw)
In-Reply-To: <20260727090601.489155-2-nora.schiffer@ew.tq-group.com>
On Mon, 2026-07-27 at 11:05 +0200, Nora Schiffer via lists.openembedded.org wrote:
> It is a bit weird that FIT_KERNEL_COMP_ALG also affects uImage creation,
> as kernel-uboot.bbclass is used for both, but fixing that would
> unnecessarily break backwards compatibility.
>
> Signed-off-by: Nora Schiffer <nora.schiffer@ew.tq-group.com>
> ---
> meta/classes-recipe/kernel-uboot.bbclass | 3 +--
> meta/conf/image-fitimage.conf | 3 +++
> 2 files changed, 4 insertions(+), 2 deletions(-)
>
> diff --git a/meta/classes-recipe/kernel-uboot.bbclass b/meta/classes-recipe/kernel-uboot.bbclass
> index fa28be1715..9beccc2dff 100644
> --- a/meta/classes-recipe/kernel-uboot.bbclass
> +++ b/meta/classes-recipe/kernel-uboot.bbclass
> @@ -4,8 +4,7 @@
> # SPDX-License-Identifier: MIT
> #
>
> -# fitImage kernel compression algorithm
> -FIT_KERNEL_COMP_ALG ?= "gzip"
> +require conf/image-fitimage.conf
>
> # Kernel image type passed to mkimage (i.e. kernel kernel_noload...)
> UBOOT_MKIMAGE_KERNEL_TYPE ?= "kernel"
> diff --git a/meta/conf/image-fitimage.conf b/meta/conf/image-fitimage.conf
> index a06d30e494..abb17186a5 100644
> --- a/meta/conf/image-fitimage.conf
> +++ b/meta/conf/image-fitimage.conf
> @@ -48,6 +48,9 @@ FIT_OS ?= "linux"
> # DTBs are provided separately in a FIT image.
> FIT_LINUX_BIN ?= "linux.bin"
>
> +# fitImage kernel compression algorithm
> +FIT_KERNEL_COMP_ALG ?= "gzip"
> +
> # Additional mkimage options for FIT image creation
> FIT_MKIMAGE_EXTRA_OPTS ?= ""
>
We're realising that the kernel classes are a bit of a tangled spiders
web and we want to improve things and clean things up.
Adding a dependency on "fit" from the "uboot" class does therefore feed
a bit backward as you note.
You mention not breaking backwards compatibility. I think given the
other work we're thinking about, it might be worth considering that and
seeing if we can avoid tangling things up even further.
Cheers,
Richard
next prev parent reply other threads:[~2026-07-30 10:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-27 9:05 [PATCH v2 0/3] kernel-fit-image: allow replacing kernel, handle compression in FIT recipe Nora Schiffer
2026-07-27 9:05 ` [PATCH v2 1/3] kernel-uboot: move FIT_KERNEL_COMP_ALG to image-fitimage.conf Nora Schiffer
2026-07-30 10:43 ` Richard Purdie [this message]
2026-07-30 11:15 ` [OE-core] " Nora Schiffer
2026-07-30 13:09 ` Richard Purdie
2026-07-30 13:35 ` Nora Schiffer
2026-07-30 13:50 ` Richard Purdie
2026-07-30 14:05 ` Nora Schiffer
2026-07-27 9:06 ` [PATCH v2 2/3] kernel-fit-image: reintroduce option to replace kernel image Nora Schiffer
2026-07-27 9:06 ` [PATCH v2 3/3] kernel-fit-extra-artifacts: skip building linux.bin if unneeded Nora Schiffer
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=f0ab7f4d7d6c72feb2b1b8122a4434db98799370.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=nora.schiffer@ew.tq-group.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=oss@ew.tq-group.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).