public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Uladzimir Bely <ubely@ilbers.de>
To: isar-users@googlegroups.com
Subject: [RFC PATCH 1/3] Don't deploy devicetree files with image
Date: Thu, 13 Jun 2024 07:19:54 +0300	[thread overview]
Message-ID: <20240613043635.21239-2-ubely@ilbers.de> (raw)
In-Reply-To: <20240613043635.21239-1-ubely@ilbers.de>

Task do_copy_boot_files deploy device tree files to the same location
for different images (e.g. -base or -debug). This causes build issue.

Stop deploying devicetree files here and let kernel recipe care about
deployment.

Signed-off-by: Uladzimir Bely <ubely@ilbers.de>
---
 meta/classes/image.bbclass | 11 -----------
 1 file changed, 11 deletions(-)

diff --git a/meta/classes/image.bbclass b/meta/classes/image.bbclass
index ff039438..bf669953 100644
--- a/meta/classes/image.bbclass
+++ b/meta/classes/image.bbclass
@@ -351,17 +351,6 @@ do_copy_boot_files() {
             cp -f "$initrd" '${DEPLOYDIR}/${INITRD_DEPLOY_FILE}'
         fi
     fi
-
-    for file in ${DTB_FILES}; do
-        dtb="$(find '${IMAGE_ROOTFS}/usr/lib' -type f \
-                    -iwholename '*linux-image-*/'${file} | head -1)"
-
-        if [ -z "$dtb" -o ! -e "$dtb" ]; then
-            die "${file} not found"
-        fi
-
-        cp -f "$dtb" "${DEPLOYDIR}/"
-    done
 }
 addtask copy_boot_files before do_rootfs_postprocess after do_rootfs_install
 
-- 
2.44.2


  reply	other threads:[~2024-06-13  4:36 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-13  4:19 [RFC PATCH 0/3] Deploy DTBs with kernel recipe Uladzimir Bely
2024-06-13  4:19 ` Uladzimir Bely [this message]
2024-06-13  4:19 ` [RFC PATCH 2/3] linux-distro: Deploy devicetree files Uladzimir Bely
2024-06-13  4:19 ` [RFC PATCH 3/3] linux-custom: " Uladzimir Bely
2024-06-21  3:20 ` [RFC PATCH 0/3] Deploy DTBs with kernel recipe Liu, Yi

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=20240613043635.21239-2-ubely@ilbers.de \
    --to=ubely@ilbers.de \
    --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