From: "'Jan Kiszka' via isar-users" <isar-users@googlegroups.com>
To: isar-users@googlegroups.com, Anton Mikanovich <amikan@ilbers.de>,
Uladzimir Bely <ubely@ilbers.de>
Subject: Re: [PATCH v5 3/3] meta: Move DTB deployment to a separate dtb-files recipe
Date: Thu, 12 Feb 2026 07:49:43 +0100 [thread overview]
Message-ID: <09e3a5af-c3a6-47db-beb9-fea9fde041a7@siemens.com> (raw)
In-Reply-To: <aYxkMEGLkQbvJyCD@abai.de>
On 11.02.26 12:12, Baurzhan Ismagulov wrote:
> On 2026-02-06 14:39, 'Jan Kiszka' via isar-users wrote:
>>> Task do_copy_boot_files was deploying DTB files into the same location
>>> for different images (e.g. -base or -debug). This causes build issue.
>>
>> But this still doesn't justify this redundant extraction. Adjust the
>> deployment paths and be done.
>
> Currently, the deployment is done in the image. Two images deploying to the
> same dtb path cause conflicts (with sstate-cache, IIRC). Detaching the
> deployment from the image and attaching it to the kernel is addressing this.
> We'll split the testcases to demonstrate this issue.
This is not the problem of the image recipes deploying, it's a problem
of the deploying to the same path. That's why I doubt this solution.
Jan
--
Siemens AG, Foundational Technologies
Linux Expert Center
--
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/09e3a5af-c3a6-47db-beb9-fea9fde041a7%40siemens.com.
next prev parent reply other threads:[~2026-02-12 6:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-06 12:27 [PATCH v5 0/3] Deploy DTBs with separate recipe Anton Mikanovich
2026-02-06 12:27 ` [PATCH v5 1/3] meta: Fix do_copy_boot_files error for different distros of same machine Anton Mikanovich
2026-02-06 12:27 ` [PATCH v5 2/3] testsuite: Add test to check dtb deployment Anton Mikanovich
2026-02-06 12:27 ` [PATCH v5 3/3] meta: Move DTB deployment to a separate dtb-files recipe Anton Mikanovich
2026-02-06 13:39 ` 'Jan Kiszka' via isar-users
2026-02-11 11:12 ` Baurzhan Ismagulov
2026-02-12 6:49 ` 'Jan Kiszka' via isar-users [this message]
2026-02-09 14:31 ` [PATCH v5 0/3] Deploy DTBs with separate recipe Zhihang Wei
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=09e3a5af-c3a6-47db-beb9-fea9fde041a7@siemens.com \
--to=isar-users@googlegroups.com \
--cc=amikan@ilbers.de \
--cc=jan.kiszka@siemens.com \
--cc=ubely@ilbers.de \
/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