From: charles.embedded@gmail.com
To: openembedded-core@lists.openembedded.org
Cc: richard.purdie@linuxfoundation.org,
Charles Dias <charlesdias.cd@outlook.com>
Subject: [PATCH] runqemu: parse QB_GRAPHICS for nographic flag
Date: Sat, 31 Jan 2026 18:11:11 -0300 [thread overview]
Message-ID: <20260131211111.1189479-1-charles.embedded@gmail.com> (raw)
From: Charles Dias <charlesdias.cd@outlook.com>
The setup_vga() function was ignoring -nographic in QB_GRAPHICS
because it only checked the command-line self.nographic flag.
This caused QB_GRAPHICS to be appended after display autodetection,
resulting in conflicting options like "-device virtio-vga -display sdl"
and "-nographic" in the same command.
Add a check after reading qemuboot.conf to detect -nographic in
QB_GRAPHICS and set self.nographic accordingly. This prevents
unnecessary display autodetection for BSPs that specify -nographic
in their machine configuration, as happens in meta-zephyr layer.
Signed-off-by: Charles Dias <charlesdias.cd@outlook.com>
---
scripts/runqemu | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/scripts/runqemu b/scripts/runqemu
index 32a3d6296a..b791abfda3 100755
--- a/scripts/runqemu
+++ b/scripts/runqemu
@@ -986,6 +986,12 @@ to your build configuration.
v = os.path.dirname(self.qemuboot)
self.set(k_upper, v)
+ # Parse QB_GRAPHICS to set internal flags if not already set by command-line
+ if not self.nographic and self.get('QB_GRAPHICS'):
+ if '-nographic' in self.get('QB_GRAPHICS'):
+ logger.debug('Detected -nographic in QB_GRAPHICS, setting nographic mode')
+ self.nographic = True
+
def validate_paths(self):
"""Ensure all relevant path variables are set"""
# When we're started with a *.qemuboot.conf arg assume that image
next reply other threads:[~2026-01-31 21:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-31 21:11 charles.embedded [this message]
2026-02-02 15:58 ` [OE-core] [PATCH] runqemu: parse QB_GRAPHICS for nographic flag Alexander Kanavin
2026-02-02 22:08 ` charles.embedded
2026-02-03 9:59 ` [OE-core] " Alexander Kanavin
2026-02-03 11:25 ` Charles Dias
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=20260131211111.1189479-1-charles.embedded@gmail.com \
--to=charles.embedded@gmail.com \
--cc=charlesdias.cd@outlook.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.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