mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Ahmad Fatoum <a.fatoum@pengutronix.de>
To: barebox@lists.infradead.org
Cc: Ahmad Fatoum <a.fatoum@pengutronix.de>
Subject: [PATCH master 1/3] test: kvx: add Labgrid env YAML for generic_defconfig
Date: Thu,  6 Aug 2026 13:28:01 +0200	[thread overview]
Message-ID: <20260806112845.3822400-1-a.fatoum@pengutronix.de> (raw)

We build for kvx in CI, but we don't yet include qemu-system-kvx.
To simplify at least manual testing, add a generic_defconfig.yaml
that correctly configures QEMU to be able to start barebox.

Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de>
---
 test/kvx/generic_defconfig.yaml | 17 +++++++++++++++++
 1 file changed, 17 insertions(+)
 create mode 100644 test/kvx/generic_defconfig.yaml

diff --git a/test/kvx/generic_defconfig.yaml b/test/kvx/generic_defconfig.yaml
new file mode 100644
index 000000000000..66b5bb308564
--- /dev/null
+++ b/test/kvx/generic_defconfig.yaml
@@ -0,0 +1,17 @@
+targets:
+  main:
+    drivers:
+      QEMUDriver:
+        qemu_bin: qemu-system-kvx
+        machine: mppa-coolidge
+        memory: 512M
+        kernel: barebox
+        display: qemu-default
+      BareboxDriver:
+        prompt: 'barebox@[^:]+:[^ ]+ '
+        bootstring: 'commandline:'
+      BareboxTestStrategy: {}
+images:
+  barebox: !template "$LG_BUILDDIR/barebox"
+imports:
+  -  ../strategy.py
-- 
2.47.3




             reply	other threads:[~2026-08-06 11:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-06 11:28 Ahmad Fatoum [this message]
2026-08-06 11:28 ` [PATCH master 2/3] kvx: select DEAD_CODE_DATA_ELIMINATION Ahmad Fatoum
2026-08-06 11:28 ` [PATCH master 3/3] dma: fix dma_realloc_coherent compile-time error on kvx Ahmad Fatoum
2026-08-06 13:08 ` [PATCH master 1/3] test: kvx: add Labgrid env YAML for generic_defconfig Sascha Hauer

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=20260806112845.3822400-1-a.fatoum@pengutronix.de \
    --to=a.fatoum@pengutronix.de \
    --cc=barebox@lists.infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox