From: Markus Armbruster <armbru@redhat.com>
To: "Thomas Weißschuh" <thomas.weissschuh@linutronix.de>
Cc: "Philippe Mathieu-Daudé" <philmd@linaro.org>,
"Daniel P. Berrangé" <berrange@redhat.com>,
"Kashyap Chamarthy" <kchamart@redhat.com>,
qemu-devel@nongnu.org
Subject: Re: [PATCH v3 2/3] docs/interop/firmware.json: add new enum FirmwareArchitecture
Date: Mon, 11 Mar 2024 14:33:08 +0100 [thread overview]
Message-ID: <87sf0wsxkb.fsf@pond.sub.org> (raw)
In-Reply-To: <20240311-qapi-firmware-json-v3-2-ceea6e35eb4a@linutronix.de> ("Thomas Weißschuh"'s message of "Mon, 11 Mar 2024 12:46:59 +0100")
Thomas Weißschuh <thomas.weissschuh@linutronix.de> writes:
> Only a small subset of all architectures supported by qemu make use of
> firmware files. Introduce and use a new enum to represent this.
>
> This also removes the dependency of firmware.json on the global qapi
> definitions.
>
> Suggested-by: Daniel P. Berrangé <berrange@redhat.com>
> Signed-off-by: Thomas Weißschuh <thomas.weissschuh@linutronix.de>
> ---
> docs/interop/firmware.json | 20 +++++++++++++++++---
> 1 file changed, 17 insertions(+), 3 deletions(-)
>
> diff --git a/docs/interop/firmware.json b/docs/interop/firmware.json
> index 0e619e8780e7..54cae6a51b43 100644
> --- a/docs/interop/firmware.json
> +++ b/docs/interop/firmware.json
> @@ -14,11 +14,13 @@
> # = Firmware
> ##
>
> -{ 'include' : 'machine.json' }
> -
> { 'pragma': {
> 'documentation-exceptions': [
> + 'FirmwareArchitecture',
Comment on the previous patch applies.
> 'FirmwareFormat'
> + ],
> + 'member-name-exceptions': [
> + 'FirmwareArchitecture'
Needed for x86_64. Fine.
> ] } }
>
> ##
> @@ -64,6 +66,18 @@
> { 'enum' : 'FirmwareDevice',
> 'data' : [ 'flash', 'kernel', 'memory' ] }
>
> +##
> +# @FirmwareArchitecture:
> +#
> +# Enumerations of architectures for which Qemu uses additional firmware files.
> +# The values are a subset of the enum SysEmuTarget.
> +#
> +# Since: 8.3
> +##
> +{ 'enum' : 'FirmwareArchitecture',
> + 'data' : [ 'aarch64', 'arm', 'i386', 'loongarch64', 'x86_64' ] }
> +
> +
> ##
> # @FirmwareTarget:
> #
> @@ -85,7 +99,7 @@
> # Since: 3.0
> ##
> { 'struct' : 'FirmwareTarget',
> - 'data' : { 'architecture' : 'SysEmuTarget',
> + 'data' : { 'architecture' : 'FirmwareArchitecture',
> 'machines' : [ 'str' ] } }
>
> ##
next prev parent reply other threads:[~2024-03-11 13:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-11 11:46 [PATCH v3 0/3] docs/interop/firmware.json: scripts/qapi-gen.py compatibility Thomas Weißschuh
2024-03-11 11:46 ` [PATCH v3 1/3] docs/interop/firmware.json: add new enum FirmwareFormat Thomas Weißschuh
2024-03-11 12:08 ` Philippe Mathieu-Daudé
2024-03-11 12:53 ` Thomas Weißschuh
2024-03-11 13:29 ` Markus Armbruster
2024-03-28 10:31 ` Thomas Weißschuh
2024-03-11 11:46 ` [PATCH v3 2/3] docs/interop/firmware.json: add new enum FirmwareArchitecture Thomas Weißschuh
2024-03-11 13:33 ` Markus Armbruster [this message]
2024-03-11 11:47 ` [PATCH v3 3/3] docs: add test for firmware.json QAPI Thomas Weißschuh
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=87sf0wsxkb.fsf@pond.sub.org \
--to=armbru@redhat.com \
--cc=berrange@redhat.com \
--cc=kchamart@redhat.com \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=thomas.weissschuh@linutronix.de \
/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).