public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Anton Mikanovich <amikan@ilbers.de>
To: "Prusty, Badrikesh" <badrikesh.prusty@siemens.com>,
	isar-users <isar-users@googlegroups.com>
Subject: Re: [PATCH v3 3/3] meta: Move DTB deployment to a separate dtb-files recipe
Date: Wed, 21 Jan 2026 17:33:49 +0200	[thread overview]
Message-ID: <8ed50d49-6bf6-4390-a953-1b5dbde8008a@ilbers.de> (raw)
In-Reply-To: <SG2PR06MB5107BA6E1B56407106193B149185A@SG2PR06MB5107.apcprd06.prod.outlook.com>

08/01/2026 15:15, Prusty, Badrikesh wrote:
> Hello Anton,
>
> Can we proceed with merging this patch?
>
> Regarding the kernel name issue, I would like to share a suggestions for
> consideration. For images that do not require kernel installation and
> are intended solely for image generation (e.g., Docker images), the
> deploy directory logic could be adapted as follows:
>
> ```
> # Deploy directory: meta/conf/bitbake.conf
> DEPLOY_DIR_IMAGE = "${DEPLOY_DIR}/images/${MACHINE}-${DISTRO}${@ (ker := d.getVar('KERNEL_NAME')) and '-' + ker or '' }"
>
> # For fixing installer image: meta-isar/classes-recipe/installer-add-rootfs.bbclass
> INSTALLER_TARGET_KERNEL ??= "${KERNEL_NAME}"
> INSTALLER_TARGET_DEPLOY_DIR_IMAGE ??= "${DEPLOY_DIR}/images/${INSTALLER_TARGET_MACHINE}-${INSTALLER_TARGET_DISTRO}${@ (ker := d.getVar('INSTALLER_TARGET_KERNEL')) and '-' + ker or '' }"
> ```
>
> This ensures that kernel name is included only when populated.
>
> Any thoughts on this?
>
>
> Many Thanks,
> Badrikesh
Hello Badrikesh,

Thanks for the suggestion. It will not work as-is because we still support
Buster, so Python 3.7 should be supported. But the idea itself was good, 
I've
reused it in v4. Please review.

-- 
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/8ed50d49-6bf6-4390-a953-1b5dbde8008a%40ilbers.de.

      reply	other threads:[~2026-01-21 15:33 UTC|newest]

Thread overview: 8+ 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
2025-10-15 14:49     ` Anton Mikanovich
2026-01-08 13:15       ` 'Prusty, Badrikesh' via isar-users
2026-01-21 15:33         ` Anton Mikanovich [this message]

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=8ed50d49-6bf6-4390-a953-1b5dbde8008a@ilbers.de \
    --to=amikan@ilbers.de \
    --cc=badrikesh.prusty@siemens.com \
    --cc=isar-users@googlegroups.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