public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: "'Jan Kiszka' via isar-users" <isar-users@googlegroups.com>
To: Anton Mikanovich <amikan@ilbers.de>, isar-users@googlegroups.com
Cc: Uladzimir Bely <ubely@ilbers.de>
Subject: Re: [PATCH v4 3/4] meta: Move DTB deployment to a separate dtb-files recipe
Date: Fri, 23 Jan 2026 15:24:16 +0100	[thread overview]
Message-ID: <145f12c6-eaa6-4954-ad9a-affedfc6b242@siemens.com> (raw)
In-Reply-To: <cde04753-26eb-4680-a92d-9adcec68b655@ilbers.de>

On 23.01.26 13:40, Anton Mikanovich wrote:
> 21/01/2026 20:27, Jan Kiszka wrote:
>>> diff --git a/meta/recipes-kernel/dtb-files/dtb-files.bb b/meta/
>>> recipes-kernel/dtb-files/dtb-files.bb
>>> new file mode 100644
>>> index 00000000..f64b4845
>>> --- /dev/null
>>> +++ b/meta/recipes-kernel/dtb-files/dtb-files.bb
>>> @@ -0,0 +1,41 @@
>>> +# This software is a part of Isar.
>>> +# Copyright (C) ilbers GmbH, 2025
>>> +#
>>> +# SPDX-License-Identifier: MIT
>>> +
>>> +inherit dpkg-raw
>>> +
>> Why does this need another package? We are repacking here already
>> packaged artifacts, and that only for the purpose of pushing them into
>> the deploy folder. This sounds strange, at best.
>>
>> Jan
> Hello Jan,
> 
> The idea was to avoid parallel execution issues by moving it from multiple
> image recipes to one recipe which will cover all the images and any type of
> kernel (prebuilt or self-built).

Still makes no sense to me: One image, one kernel, one dtb deployment -
isn't that what patch 1 ensures?

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/145f12c6-eaa6-4954-ad9a-affedfc6b242%40siemens.com.

  reply	other threads:[~2026-01-23 14:24 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-21 15:30 [PATCH v4 0/4] Deploy DTBs with separate recipe Anton Mikanovich
2026-01-21 15:30 ` [PATCH v4 1/4] meta: Fix do_copy_boot_files error for different distros of same machine Anton Mikanovich
2026-01-21 15:30 ` [PATCH v4 2/4] testsuite: Add test to check dtb deployment Anton Mikanovich
2026-01-21 15:30 ` [PATCH v4 3/4] meta: Move DTB deployment to a separate dtb-files recipe Anton Mikanovich
2026-01-21 18:27   ` 'Jan Kiszka' via isar-users
2026-01-23 12:40     ` Anton Mikanovich
2026-01-23 14:24       ` 'Jan Kiszka' via isar-users [this message]
2026-01-21 15:30 ` [PATCH v4 4/4] installer: Fix DEPLOY_DIR_IMAGE path for target image Anton Mikanovich
2026-01-21 18:29   ` 'Jan Kiszka' via isar-users
2026-01-23 12:44     ` Anton Mikanovich
2026-01-23 14:26       ` 'Jan Kiszka' via isar-users
2026-01-22 16:53 ` [PATCH v4 0/4] 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=145f12c6-eaa6-4954-ad9a-affedfc6b242@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