From: Trevor Woerner <twoerner@gmail.com>
To: yocto@lists.yoctoproject.org
Subject: [meta-rockchip][PATCH] rkbin:rk3308: pre-cleanup
Date: Fri, 3 Nov 2023 11:21:30 -0400 [thread overview]
Message-ID: <20231103152130.9912-1-twoerner@gmail.com> (raw)
Since 2 recipes can provide the same rk3308-specific blobs, switching
between them can potentially cause: "... is trying to install files into a
shared area when those files already exist" errors. Perform a pre-cleanup
in both recipes so they don't step on each others' toes.
Signed-off-by: Trevor Woerner <twoerner@gmail.com>
---
recipes-bsp/rkbin/rk3308-rkbin_git.bb | 5 +++++
recipes-bsp/rkbin/rockchip-rkbin_git.bb | 5 +++++
2 files changed, 10 insertions(+)
diff --git a/recipes-bsp/rkbin/rk3308-rkbin_git.bb b/recipes-bsp/rkbin/rk3308-rkbin_git.bb
index c6b05b242738..65ee136eff7c 100644
--- a/recipes-bsp/rkbin/rk3308-rkbin_git.bb
+++ b/recipes-bsp/rkbin/rk3308-rkbin_git.bb
@@ -26,6 +26,11 @@ PACKAGES = "${PN}"
ALLOW_EMPTY:${PN} = "1"
do_deploy:rk3308() {
+ # cleanup first
+ rm -f ${DEPLOY_DIR_IMAGE}/bl31-rk3308.elf
+ rm -f ${DEPLOY_DIR_IMAGE}/tee-rk3308.bin
+ rm -f ${DEPLOY_DIR_IMAGE}/ddr-rk3308.bin
+
# Prebuilt TF-A
install -m 644 ${S}/bin/rk33/rk3308_bl31_v*.elf ${DEPLOYDIR}/bl31-rk3308.elf
# Prebuilt OPTEE-OS
diff --git a/recipes-bsp/rkbin/rockchip-rkbin_git.bb b/recipes-bsp/rkbin/rockchip-rkbin_git.bb
index f1609c7a4957..3f842d669c76 100644
--- a/recipes-bsp/rkbin/rockchip-rkbin_git.bb
+++ b/recipes-bsp/rkbin/rockchip-rkbin_git.bb
@@ -27,6 +27,11 @@ PACKAGES = "${PN}"
ALLOW_EMPTY:${PN} = "1"
do_deploy:rk3308() {
+ # cleanup first
+ rm -f ${DEPLOY_DIR_IMAGE}/bl31-rk3308.elf
+ rm -f ${DEPLOY_DIR_IMAGE}/tee-rk3308.bin
+ rm -f ${DEPLOY_DIR_IMAGE}/ddr-rk3308.bin
+
# Prebuilt TF-A
install -m 644 ${S}/bin/rk33/rk3308_bl31_v*.elf ${DEPLOYDIR}/bl31-rk3308.elf
# Prebuilt OPTEE-OS
--
2.41.0.327.gaa9166bcc0ba
reply other threads:[~2023-11-03 15:21 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20231103152130.9912-1-twoerner@gmail.com \
--to=twoerner@gmail.com \
--cc=yocto@lists.yoctoproject.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.