From: Uladzimir Bely <ubely@ilbers.de>
To: isar-users@googlegroups.com
Subject: [RFC PATCH 0/3] Deploy DTBs with kernel recipe
Date: Thu, 13 Jun 2024 07:19:53 +0300 [thread overview]
Message-ID: <20240613043635.21239-1-ubely@ilbers.de> (raw)
Image task "do_copy_boot_files" is used to deploy kernel, initrd and
devicetree binaries to deploy directory.
When different images for the same target are built (e.g., "-base" and
"-debug") in parallel, this causes issues with DTB deployment since
they have no any image name specific stuff in the path, unlike kernel
and initrd.
Here we make kernel recipes (that are original source of these files)
responcible for DTB deployment.
Related topics on maillist:
https://groups.google.com/g/isar-users/c/4BRDM02xC40
https://groups.google.com/g/isar-users/c/qAnjahjjfsw
https://groups.google.com/g/isar-users/c/ZMD4XY4dKWQ
https://groups.google.com/g/isar-users/c/PSGU_AcdPZ8
https://groups.google.com/g/isar-users/c/Va0Ue-ISYeA
To fix the case when different distro use same namings for DTB, this
patchset should be merged with "[PATCH] Fix do_copy_boot_files error":
https://groups.google.com/g/isar-users/c/Va0Ue-ISYeA
Uladzimir Bely (3):
Don't deploy devicetree files with image
linux-distro: Deploy devicetree files
linux-custom: Deploy devicetree files
meta/classes/image.bbclass | 11 --------
meta/recipes-kernel/linux/linux-custom.inc | 13 +++++++++
meta/recipes-kernel/linux/linux-distro.bb | 31 ++++++++++++++++++++++
3 files changed, 44 insertions(+), 11 deletions(-)
--
2.44.2
next 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 Uladzimir Bely [this message]
2024-06-13 4:19 ` [RFC PATCH 1/3] Don't deploy devicetree files with image Uladzimir Bely
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-1-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