public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: "'Badrikesh Prusty' via isar-users" <isar-users@googlegroups.com>
To: isar-users <isar-users@googlegroups.com>
Subject: Re: [PATCH v3 3/3] meta: Move DTB deployment to a separate dtb-files recipe
Date: Wed, 15 Oct 2025 02:55:26 -0700 (PDT)	[thread overview]
Message-ID: <ca3169ff-80f9-4b91-bfee-670c0fbc377bn@googlegroups.com> (raw)
In-Reply-To: <20251008085507.1017500-4-amikan@ilbers.de>


[-- Attachment #1.1: Type: text/plain, Size: 840 bytes --]

Hello Anton,

Thank you for the patch.
With the changes, the machine base images are building as expected, and we 
are able to build multiple images with different kernels and distros.  

For isar-installer-image, the bundling process is still searching for 
images in the old deploy directory path:  

meta-isar/classes/installer-add-rootfs.bbclass
---
INSTALLER_TARGET_DEPLOY_DIR_IMAGE ??= 
"${DEPLOY_DIR}/images/${INSTALLER_TARGET_MACHINE}"

Please have a look.

Thanks,
Badrikesh

-- 
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/ca3169ff-80f9-4b91-bfee-670c0fbc377bn%40googlegroups.com.

[-- Attachment #1.2: Type: text/html, Size: 1280 bytes --]

  reply	other threads:[~2025-10-15 14:21 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-08  8:55 [PATCH v3 0/3] Deploy DTBs with separate recipe Anton Mikanovich
2025-10-08  8:55 ` [PATCH v3 1/3] meta: Fix do_copy_boot_files error for different distros of same machine Anton Mikanovich
2025-10-08  8:55 ` [PATCH v3 2/3] testsuite: Add test to check dtb deployment Anton Mikanovich
2025-10-08  8:55 ` [PATCH v3 3/3] meta: Move DTB deployment to a separate dtb-files recipe Anton Mikanovich
2025-10-15  9:55   ` 'Badrikesh Prusty' via isar-users [this message]
2025-10-15 14:49     ` Anton Mikanovich

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=ca3169ff-80f9-4b91-bfee-670c0fbc377bn@googlegroups.com \
    --to=isar-users@googlegroups.com \
    --cc=badrikesh.prusty@siemens.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