Re: [PATCH v4 0/4] Deploy DTBs with separate recipe

[Zhihang Wei <wzh@ilbers.de>]

On 1/21/26 16:30, Anton Mikanovich wrote:
> Image task "do_copy_boot_files" is used to deploy kernel, initrd and
> devicetree binaries to deploy directory.
>
> When different images for the same target are built (e.g., "-base" and
> "-debug") in parallel, this causes issues with DTB deployment since
> they have no any image_name-specific stuff in the path, unlike kernel
> and initrd.
>
> Here we make a separate recipe responsible for the DTB deployment.
> DTBs are extracted from the kernel package (provided by distro or
> self-built).
>
> The recipe 'dtb-files' is MACHINE-dependent, so different DTB_FILES
> may be deployed for different machines. At the same time, all these
> 'dtb-files-${MACHINE}' targets depend on the same kernel package, so
> it is built only once.
>
> The case when different distros (e.g., bullseye/bookworm) are using the
> same name for DTB binaries is covered by the patch 1. It also covers
> the case when image uses different kernel suffix (e.g., "realtime"
> option for the kernel in some downstreams).
>
> Related topics on maillist:
>
> https://groups.google.com/g/isar-users/c/ht3YmKZcJlM
> https://groups.google.com/g/isar-users/c/4BRDM02xC40
> https://groups.google.com/g/isar-users/c/qAnjahjjfsw
> https://groups.google.com/g/isar-users/c/ZMD4XY4dKWQ
> https://groups.google.com/g/isar-users/c/PSGU_AcdPZ8
> https://groups.google.com/g/isar-users/c/Va0Ue-ISYeA
> https://groups.google.com/g/isar-users/c/ixzytHYnTmI
>
> Changes since v3:
> - Rebase on next.
> - Fix target deploy dir path for installer.
>
> Changes since v2:
> - Patch 1: Consider also kernel suffix.
> - Patch 2: Use separate testcase for possible dtb clashes.
> - Minor cosmetic fixes.
>
> Changes since v1:
> - Separate `dtb-files` recipe used instead of linux one
> - Included older "[PATCH] Fix do_copy_boot_files error" into the
> series ( https://groups.google.com/g/isar-users/c/Va0Ue-ISYeA )
>
> Anton Mikanovich (2):
>    testsuite: Add test to check dtb deployment
>    installer: Fix DEPLOY_DIR_IMAGE path for target image
>
> Ilia Skochilov (1):
>    meta: Fix do_copy_boot_files error for different distros of same
>      machine
>
> Uladzimir Bely (1):
>    meta: Move DTB deployment to a separate dtb-files recipe
>
>   RECIPE-API-CHANGELOG.md                       | 15 +++++++
>   .../installer-add-rootfs.bbclass              |  4 +-
>   meta/classes-recipe/image.bbclass             | 15 +++----
>   meta/conf/bitbake.conf                        |  2 +-
>   meta/recipes-kernel/dtb-files/dtb-files.bb    | 41 +++++++++++++++++++
>   testsuite/citest.py                           | 23 +++++++++++
>   6 files changed, 88 insertions(+), 12 deletions(-)
>   create mode 100644 meta/recipes-kernel/dtb-files/dtb-files.bb
>

Hi,

The patchset is causing all 3 tests in InitRdTest test suite to fail, all
because of "initrd image not found". I think it's because of the change of
DEPLOY_DIR_IMAGE. Need to check that in detail.

Also it causes |NoCrossTest.test_nocross| to fail.
Failed job: 
|isar-image-ci-qemuamd64-iso/1.0-r0/temp/log.do_image_wic.3271529|
|Log follows:|
|||INFO: Creating image(s)...
ERROR: _exec_cmd: cd 
/tmp/isar-image-ci-debian-bookworm-qemuamd64-iso.wic/tmp.wic.2cow9dtb/INITRD 
&& find . | cpio -o -H newc -R root:root 
 >/tmp/isar-image-ci-debian-bookworm-qemuamd64-iso.wic/tmp.wic.2cow9dtb/initrd.cpio 
returned '127' instead of 0
output: /bin/sh: 1: cpio: not found.|

Zhihang

-- 
You received this message because you are subscribed to the Google Groups "isar-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to isar-users+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/isar-users/99d79c38-ffe4-4bc6-a1d0-6edc50e536ec%40ilbers.de.