public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: "Mathieu Dubois-Briand" <mathieu.dubois-briand@bootlin.com>
To: <viswanath.kraleti@oss.qualcomm.com>,
	<openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core][meta][PATCH v2] uki.bbclass: make DTB packaging optional
Date: Thu, 12 Mar 2026 08:43:18 +0100	[thread overview]
Message-ID: <DH0MVS45J75E.3OIX034VEUGS9@bootlin.com> (raw)
In-Reply-To: <20260311122507.2121997-1-viswanath.kraleti@oss.qualcomm.com>

On Wed Mar 11, 2026 at 1:25 PM CET, Viswanath Kraleti via lists.openembedded.org wrote:
> According to the Unified Kernel Image (UKI) specification [1], including
> a compiled device tree in the .dtb section of a UKI is optional. However,
> the current implementation always packages device trees listed in
> KERNEL_DEVICETREE into the UKI by default. This makes uki.bbclass
> unsuitable for systems that rely on firmware-provided DTBs and do not
> want a DTB embedded in the UKI.
>
> Fix this by introducing a new UKI_DEVICETREE variable to control device
> tree packaging. The .dtb section is now populated from UKI_DEVICETREE
> instead of KERNEL_DEVICETREE. Users who do not want DTBs included in the
> UKI can override UKI_DEVICETREE to an empty value from their recipes.
>
> Update the UKI selftests accordingly, as QEMU does not provide a device
> tree to embed.
>
> [1] https://uapi-group.org/specifications/specs/unified_kernel_image/
>
> Signed-off-by: Viswanath Kraleti <viswanath.kraleti@oss.qualcomm.com>
> ---

Hi Viswanath,

Thanks for the new version.

It looks like one of the selftest is still failing:

2026-03-11 20:52:20,986 - oe-selftest - INFO - wic.Wic2.test_efi_plugin_unified_kernel_image_qemu (subunit.RemotedTestCase)
2026-03-11 20:52:20,987 - oe-selftest - INFO -  ... FAIL
...
2026-03-11 20:52:20,987 - oe-selftest - INFO - 13: 48/73 559/681 (145.46s) (0 failed) (wic.Wic2.test_efi_plugin_unified_kernel_image_qemu)
2026-03-11 20:52:20,987 - oe-selftest - INFO - testtools.testresult.real._StringException: Traceback (most recent call last):
  File "/srv/pokybuild/yocto-worker/oe-selftest-debian/build/layers/openembedded-core/meta/lib/oeqa/core/decorator/__init__.py", line 35, in wrapped_f
    return func(*args, **kwargs)
  File "/srv/pokybuild/yocto-worker/oe-selftest-debian/build/layers/openembedded-core/meta/lib/oeqa/selftest/cases/wic.py", line 1561, in test_efi_plugin_unified_kernel_image_qemu
    bitbake('core-image-base ovmf')
  File "/srv/pokybuild/yocto-worker/oe-selftest-debian/build/layers/openembedded-core/meta/lib/oeqa/utils/commands.py", line 236, in bitbake
    return runCmd(cmd, ignore_status, timeout, output_log=output_log, **options)
  File "/srv/pokybuild/yocto-worker/oe-selftest-debian/build/layers/openembedded-core/meta/lib/oeqa/utils/commands.py", line 214, in runCmd
    raise AssertionError("Command '%s' returned non-zero exit status %d:\n%s" % (command, result.status, exc_output))
AssertionError: Command 'bitbake  core-image-base ovmf' returned non-zero exit status 1:
...
ERROR: core-image-base-1.0-r0 do_uki: ERROR: cannot find /srv/pokybuild/yocto-worker/oe-selftest-debian/build/build-st-4172893/tmp/deploy/images/qemux86-64/${KERNEL_DEVICETREE}.

https://autobuilder.yoctoproject.org/valkyrie/#/builders/35/builds/3383
https://autobuilder.yoctoproject.org/valkyrie/#/builders/48/builds/3273

Can you have a look at the issue?

Thanks,
Mathieu

-- 
Mathieu Dubois-Briand, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com



      reply	other threads:[~2026-03-12  7:43 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-11 12:25 [OE-core][meta][PATCH v2] uki.bbclass: make DTB packaging optional Viswanath Kraleti
2026-03-12  7:43 ` Mathieu Dubois-Briand [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=DH0MVS45J75E.3OIX034VEUGS9@bootlin.com \
    --to=mathieu.dubois-briand@bootlin.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=viswanath.kraleti@oss.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