From: Anton Mikanovich <amikan@ilbers.de>
To: isar-users@googlegroups.com
Cc: Anton Mikanovich <amikan@ilbers.de>
Subject: [PATCH] beagleplay: Add missing COMPATIBLE_MACHINE
Date: Thu, 23 May 2024 13:35:14 +0300 [thread overview]
Message-ID: <20240523103514.879779-1-amikan@ilbers.de> (raw)
Optee-os and trusted-firmware-a recipes for beagleplay target are
missing COMPATIBLE_MACHINE value while PROVIDES value use current
machine value which is the same for all recipes. This makes bitbake
confusing to match recipes for optee-os and trusted-firmware-a
packages.
Signed-off-by: Anton Mikanovich <amikan@ilbers.de>
---
meta-isar/recipes-bsp/optee-os/optee-os-beagleplay_4.0.0.bb | 2 ++
.../trusted-firmware-a/trusted-firmware-a-beagleplay_2.10.bb | 2 ++
2 files changed, 4 insertions(+)
diff --git a/meta-isar/recipes-bsp/optee-os/optee-os-beagleplay_4.0.0.bb b/meta-isar/recipes-bsp/optee-os/optee-os-beagleplay_4.0.0.bb
index ef420687..dc7f3fd3 100644
--- a/meta-isar/recipes-bsp/optee-os/optee-os-beagleplay_4.0.0.bb
+++ b/meta-isar/recipes-bsp/optee-os/optee-os-beagleplay_4.0.0.bb
@@ -16,3 +16,5 @@ OPTEE_PLATFORM = "k3"
OPTEE_EXTRA_BUILDARGS = " \
TEE_IMPL_VERSION=${PV} \
CFG_ARM64_core=y CFG_USER_TA_TARGETS=ta_arm64"
+
+COMPATIBLE_MACHINE = "beagleplay"
diff --git a/meta-isar/recipes-bsp/trusted-firmware-a/trusted-firmware-a-beagleplay_2.10.bb b/meta-isar/recipes-bsp/trusted-firmware-a/trusted-firmware-a-beagleplay_2.10.bb
index 035095b6..aae3e2a8 100644
--- a/meta-isar/recipes-bsp/trusted-firmware-a/trusted-firmware-a-beagleplay_2.10.bb
+++ b/meta-isar/recipes-bsp/trusted-firmware-a/trusted-firmware-a-beagleplay_2.10.bb
@@ -13,3 +13,5 @@ S = "${WORKDIR}/git"
TF_A_PLATFORM = "k3"
TF_A_EXTRA_BUILDARGS = "CFG_ARM64=y TARGET_BOARD=lite SPD=opteed"
TF_A_BINARIES = "lite/release/bl31.bin"
+
+COMPATIBLE_MACHINE = "beagleplay"
--
2.34.1
next reply other threads:[~2024-05-23 10:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-23 10:35 Anton Mikanovich [this message]
2024-05-30 5:53 ` Uladzimir Bely
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=20240523103514.879779-1-amikan@ilbers.de \
--to=amikan@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