From: "Philippe Mathieu-Daudé" <philmd@linaro.org>
To: QEMU Developers <qemu-devel@nongnu.org>
Cc: "Laurent Vivier" <laurent@vivier.eu>,
"Mark Cave-Ayland" <mark.cave-ayland@ilande.co.uk>,
"Daniel Henrique Barboza" <danielhb413@gmail.com>,
"Markus Armbruster" <armbru@redhat.com>,
"Daniel P. Berrangé" <berrange@redhat.com>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Peter Maydell" <peter.maydell@linaro.org>,
qemu-ppc@nongnu.org, "Artyom Tarasenko" <atar4qemu@gmail.com>,
"Alex Bennée" <alex.bennee@linaro.org>
Subject: Any plan for command line '-g' option (graphical resolution and depth)?
Date: Thu, 20 Feb 2025 10:20:51 +0100 [thread overview]
Message-ID: <97e66ba5-488f-4246-b4d9-466d29a86dff@linaro.org> (raw)
Hi,
QEMU provides the global '-g' CLI option:
$ qemu-system-foo --help
-g WxH[xDEPTH] Set the initial graphical resolution and depth
This option is used to pass resolution/depth information to guest
firmwares in the machines defined in the following files:
hw/ppc/mac_newworld.c
hw/ppc/mac_oldworld.c
hw/ppc/prep.c
hw/ppc/spapr.c
hw/sparc/sun4m.c
hw/sparc64/sun4u.c
Examples:
- hw/ppc/spapr.c:1102:
_FDT(fdt_setprop_cell(fdt, c, "qemu,graphic-width", graphic_width));
- hw/sparc64/sun4u.c:716:
fw_cfg_add_i16(fw_cfg, FW_CFG_SPARC64_WIDTH, graphic_width);
Obviously we have default values, which are different per architecture!
Clearly these ought to be machine properties.
It is also used to set TYPE_NUBUS_MACFB properties in hw/m68k/q800.c.
Here i suppose we could directly use '-global nubus-macfb.width=value'
etc. although I'm not sure it is the recommended way.
Should we start deprecating '-g' as a whole?
Regards,
Phil.
next reply other threads:[~2025-02-20 9:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-20 9:20 Philippe Mathieu-Daudé [this message]
2025-02-20 9:50 ` Any plan for command line '-g' option (graphical resolution and depth)? Paolo Bonzini
2025-02-20 10:22 ` Philippe Mathieu-Daudé
2025-02-20 11:28 ` Gerd Hoffmann
2025-02-20 11:13 ` Mark Cave-Ayland
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=97e66ba5-488f-4246-b4d9-466d29a86dff@linaro.org \
--to=philmd@linaro.org \
--cc=alex.bennee@linaro.org \
--cc=armbru@redhat.com \
--cc=atar4qemu@gmail.com \
--cc=berrange@redhat.com \
--cc=danielhb413@gmail.com \
--cc=laurent@vivier.eu \
--cc=mark.cave-ayland@ilande.co.uk \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.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;
as well as URLs for NNTP newsgroup(s).