Re: [PATCH v9 0/3] Deploy DTBs and other image artifacts into subdirs to avoid conflicts

["'MOESSBAUER, Felix' via isar-users" <isar-users@googlegroups.com>]

On Thu, 2026-04-09 at 17:35 +0200, Zhihang Wei wrote:
> On 4/8/26 15:10, Jan Kiszka wrote:
> > On 07.04.26 16:29, Quirin Gylstorff wrote:
> > > Hi,
> > > 
> > > On 4/1/26 12:49 PM, Zhihang Wei wrote:
> > > > Image task "do_copy_boot_files" deploys kernel, initrd, and device tree
> > > > binaries to the deploy directory.
> > > > 
> > > > When different images for the same target (e.g., "-base" and "-debug")
> > > > are built in parallel, DTB deployment may fail because DTBs do not
> > > > contain image-specific components in their filenames, unlike the kernel
> > > > and initrd. As a result, artifacts from different builds may be written
> > > > to the same location.
> > > > 
> > > > Here we deploy the DTBs and other image artifacts to subdirectories,
> > > > with names of distro image encoded to the path.
> > > > 
> > > > Note that this results in separate copies of the same artifacts being
> > > > deployed for each image build.
> > > > 
> > > This breaks isar-cip-core with release 1.0 with the unified kernel build
> > > as a custom initrd is no longer part of the same directory structure as
> > > the rest of the image. As the custom initramfs is a separate package it
> > > cannot aquire the PN of the rootfs. See https://github.com/ilbers/isar/
> > > blob/6504321e85b5fdc3bb5a83f042b77cb39cd11a6f/meta/classes-recipe/
> > > imagetypes_wic.bbclass#L215.
> > > 
> > > Also merge_wic_sbom does no longer work with a custom initrd.
> > > 
> > The RECIPE-API-CHANGLOG says:
> > 
> > > Artifacts that do not belong to a full image (e.g. isar-image-base,
> > > isar-image-ci) remain unchanged. For example, a customized initramfs
> > > built independently is not affected.
> > And this is the problem: Customized initramfs logically belonged to full
> > images, and so it was possible to address them DEPLOY_DIR_IMAGE. Now
> > they are "somewhere" - namely under the OE-standard DEPLOY_DIR_IMAGE,
> > but there also with the traditional image file naming, flat.
> "remain unchanged" here means the customized initramfs keep the same
> filenames and paths as before.
> 
> Customized initramfs are built by their own recipes. While building a
> full image may trigger the build of a customized initramfs, they can
> also be built separately. In contrast, the default initramfs is not a
> standalone recipe but a task within the image build process. So
> technically, customized initramfs are independent artifacts.
> 
> If CIP core associates a specific customized initramfs with an image
> via DEPLOY_DIR_IMAGE, this assumption is affected by the new layout and
> needs to be adapted accordingly.

> 
Hi, as I already wrote in [1], the root cause of the bug is that there
is currently no way to couple the path of the deployed initrd and the
imaging step. We previously relied on well-known path coincidence by
basically guessing how the initrd is named and checking if there is one
at the guessed path.

If the path is no longer predictable (with the Deploy DTBs patchset),
we cannot find the initrd.

What we actually need is a way to pass down a variable to both the
image and the initrd. This variable could be defined in local conf or
machine conf. Semantically, it belongs to the machine conf as there
also the kernel is selected. I can try to come up with a PoC for that,
but as of now, ISAR v1.0 is simply broken!

[1] 
https://github.com/ilbers/isar/commit/8986f02c27d0e94fb4945690b572d9e5a8cebc2f

Best regards,
Felix

-- 
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/767da583999ea8b35916395d040d46052d60e1cb.camel%40siemens.com.