From: Uladzimir Bely <ubely@ilbers.de>
To: isar-users@googlegroups.com
Subject: [RFC PATCH 3/3] linux-custom: Deploy devicetree files
Date: Thu, 13 Jun 2024 07:19:56 +0300 [thread overview]
Message-ID: <20240613043635.21239-4-ubely@ilbers.de> (raw)
In-Reply-To: <20240613043635.21239-1-ubely@ilbers.de>
Deploy devicetree files with the custom kernel package instead of
using image recipe.
Signed-off-by: Uladzimir Bely <ubely@ilbers.de>
---
meta/recipes-kernel/linux/linux-custom.inc | 13 +++++++++++++
1 file changed, 13 insertions(+)
diff --git a/meta/recipes-kernel/linux/linux-custom.inc b/meta/recipes-kernel/linux/linux-custom.inc
index 647f09dd..c45dad4b 100644
--- a/meta/recipes-kernel/linux/linux-custom.inc
+++ b/meta/recipes-kernel/linux/linux-custom.inc
@@ -278,3 +278,16 @@ EOF
do_dpkg_source:prepend() {
dpkg_configure_kernel
}
+
+do_deploy[dirs] = "${DEPLOY_DIR_IMAGE}"
+do_deploy[cleandirs] = "${WORKDIR}/deploy"
+do_deploy() {
+ dpkg --fsys-tarfile ${WORKDIR}/linux-image-${KERNEL_NAME}_${CHANGELOG_V}_${PACKAGE_ARCH}.deb | \
+ tar --wildcards --extract --directory ${WORKDIR}/deploy ./usr/lib/linux-image-*
+ for dtb in ${DTB_FILES}; do
+ mkdir -p ${DEPLOY_DIR_IMAGE}/$(dirname ${dtb})
+ find ${WORKDIR}/deploy/usr/lib/linux-image* -path "*${dtb}" -print \
+ -exec cp {} ${DEPLOY_DIR_IMAGE}/${dtb} \;
+ done
+}
+addtask deploy before do_deploy_deb after do_dpkg_build
--
2.44.2
next prev parent 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 ` [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 ` Uladzimir Bely [this message]
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-4-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