public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Baurzhan Ismagulov <ibr@radix50.net>
To: isar-users@googlegroups.com
Subject: Re: Duplicated dtb files issue for multiple confiugrations
Date: Mon, 10 Jun 2024 12:10:46 +0200	[thread overview]
Message-ID: <ZmbRJtTCp6rupmfD@ilbers.de> (raw)
In-Reply-To: <c790f769-1c72-4ea0-980e-7266f9b3ed34n@googlegroups.com>

On 2024-06-06 00:24, 'Yi Liu' via isar-users wrote:
> Thanks for the suggestion. This patch has been verified that can solve the 
> issue for my case. 
> 
> I will keep it as a temporary solution until the better one is found.

Thanks Liu Yi for the feedback,

To summarize the topics, we're experiencing two different issues:

1. Two images, same machine: Same dtb overwritten in deploy by image.bbclass --
   this thread.

   Proposals:

   - Split by image
     - Possibly with on/off switch
   - Deploy in kernel recipe

2. Different dtbs overwritten in deploy.

   Addressed by splitting by machine-distro:
   https://patchwork.isar-build.org/project/isar/patch/20240131144459.2386220-1-iskochilov@ilbers.de/

Deploying in the kernel recipe would solve #1 without splitting the deploy dir.
We'll be sharing our progress on this.

We've checked the use case of rebuilding into a dirty deploy dir with a
different config for the same machine/distro and didn't encounter any issues.
If this is still relevant, we'd like to have the steps to reproduce.

With kind regards,
Baurzhan

      reply	other threads:[~2024-06-10 10:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-03 12:46 yi liu
2024-06-04 12:38 ` Uladzimir Bely
2024-06-05 16:23   ` Jan Kiszka
2024-06-06  7:24   ` Yi Liu
2024-06-10 10:10     ` Baurzhan Ismagulov [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=ZmbRJtTCp6rupmfD@ilbers.de \
    --to=ibr@radix50.net \
    --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