From: Marek Vasut <marek.vasut@mailbox.org>
To: openembedded-core@lists.openembedded.org
Cc: Marek Vasut <marek.vasut@mailbox.org>,
Adrian Freihofer <adrian.freihofer@siemens.com>,
Richard Purdie <richard.purdie@linuxfoundation.org>,
Yoann Congal <yoann.congal@smile.fr>
Subject: [PATCH] kernel-fit-image.bbclass: Do not include kernel property in DTBO config subnodes
Date: Wed, 17 Jun 2026 00:06:38 +0200 [thread overview]
Message-ID: <20260616220700.41516-1-marek.vasut@mailbox.org> (raw)
The OE 5.0 implementation of fitImage generation did not include the
kernel property in DTBO configuration node subnodes, while the current
OE 6.0 implementation does. The previous implementation was correct,
because kernel together with only a DTBO overlay can not form bootable
result. The kernel property should only be part of the configuration
subnode which includes both kernel and DTB. Fix this.
Fixes: 05d0c7342d76 ("kernel-fit-image.bbclass: add a new FIT image implementation")
Signed-off-by: Marek Vasut <marek.vasut@mailbox.org>
---
Cc: Adrian Freihofer <adrian.freihofer@siemens.com>
Cc: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: Yoann Congal <yoann.congal@smile.fr>
---
NOTE: This should ideally be added into OE 6.0 too
---
meta/lib/oe/fitimage.py | 7 ++++++-
1 file changed, 6 insertions(+), 1 deletion(-)
diff --git a/meta/lib/oe/fitimage.py b/meta/lib/oe/fitimage.py
index 881d0eae0ab..d7e21171ab9 100644
--- a/meta/lib/oe/fitimage.py
+++ b/meta/lib/oe/fitimage.py
@@ -425,8 +425,13 @@ class ItsNodeRootKernel(ItsNode):
opt_props = {}
conf_desc = []
sign_entries = []
+ include_kernel = 1
- if self._kernel:
+ # DTBO configuration sections do not include kernel property
+ if dtb and os.path.splitext(dtb.name)[1] == ".dtbo":
+ include_kernel = 0
+
+ if self._kernel and include_kernel:
conf_desc.append("Linux kernel")
opt_props["kernel"] = self._kernel.name
if self._sign_enable:
--
2.53.0
reply other threads:[~2026-06-16 22:07 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20260616220700.41516-1-marek.vasut@mailbox.org \
--to=marek.vasut@mailbox.org \
--cc=adrian.freihofer@siemens.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.org \
--cc=yoann.congal@smile.fr \
/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