From: Francesco Valla <francesco@valla.it>
To: openembedded-core@lists.openembedded.org
Cc: Adrian Freihofer <adrian.freihofer@siemens.com>,
Francesco Castagnotto <fcastagnotto@linux.com>,
Francesco Valla <francesco@valla.it>
Subject: [PATCH RFC 3/4] recipes-test: add bootconfig-test recipe
Date: Thu, 19 Mar 2026 00:30:51 +0100 [thread overview]
Message-ID: <20260319-bootconfig-v1-3-a4d467c3f0ba@valla.it> (raw)
In-Reply-To: <20260319-bootconfig-v1-0-a4d467c3f0ba@valla.it>
Add a test recipe deploying a fixed bootconfig source file to
DEPLOY_DIR_IMAGE, to be used in tests that expect a bootconfig to be
available.
Signed-off-by: Francesco Valla <francesco@valla.it>
---
.../recipes-test/bootconfig/bootconfig-test.bb | 20 ++++++++++++++++++++
.../bootconfig/bootconfig-test/bootconfig-test.txt | 6 ++++++
2 files changed, 26 insertions(+)
diff --git a/meta-selftest/recipes-test/bootconfig/bootconfig-test.bb b/meta-selftest/recipes-test/bootconfig/bootconfig-test.bb
new file mode 100644
index 0000000000000000000000000000000000000000..0cf74fa93652009466220f21001923a81d628a2e
--- /dev/null
+++ b/meta-selftest/recipes-test/bootconfig/bootconfig-test.bb
@@ -0,0 +1,20 @@
+SUMMARY = "Test bootconfig"
+DESCRIPTION = "This generates a dummy bootconfig to be used to for testing."
+LICENSE = "MIT"
+
+SRC_URI = "file://bootconfig-test.txt"
+
+EXCLUDE_FROM_WORLD = "1"
+
+inherit deploy nopackages
+
+do_configure[noexec] = "1"
+do_compile[noexec] = "1"
+deltask do_stash_locale
+deltask do_install
+deltask do_populate_sysroot
+
+do_deploy() {
+ install -m0664 ${UNPACKDIR}/bootconfig-test.txt ${DEPLOYDIR}/bootconfig-test.txt
+}
+addtask deploy after do_unpack before do_build
diff --git a/meta-selftest/recipes-test/bootconfig/bootconfig-test/bootconfig-test.txt b/meta-selftest/recipes-test/bootconfig/bootconfig-test/bootconfig-test.txt
new file mode 100644
index 0000000000000000000000000000000000000000..c194018b0bd0e225aaf01a49dff78fcaebe8a7d4
--- /dev/null
+++ b/meta-selftest/recipes-test/bootconfig/bootconfig-test/bootconfig-test.txt
@@ -0,0 +1,6 @@
+kernel {
+ root = 01234567-89ab-cdef-0123-456789abcd
+}
+init {
+ splash
+}
--
2.53.0
next prev parent reply other threads:[~2026-03-18 23:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-18 23:30 [PATCH RFC 0/4] Add support for bootconfig on initramfs and FIT images Francesco Valla
2026-03-18 23:30 ` [PATCH RFC 1/4] bootconfig: add recipe Francesco Valla
2026-03-19 8:54 ` Freihofer, Adrian
2026-03-20 13:27 ` Francesco Valla
2026-03-18 23:30 ` [PATCH RFC 2/4] image_types: add bootconfig conversion type Francesco Valla
2026-03-18 23:30 ` Francesco Valla [this message]
2026-03-18 23:30 ` [PATCH RFC 4/4] kernel-fit-image: add bootconfig support Francesco Valla
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=20260319-bootconfig-v1-3-a4d467c3f0ba@valla.it \
--to=francesco@valla.it \
--cc=adrian.freihofer@siemens.com \
--cc=fcastagnotto@linux.com \
--cc=openembedded-core@lists.openembedded.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.