qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Philippe Mathieu-Daudé" <philmd@linaro.org>
To: Gerd Hoffmann <kraxel@redhat.com>, qemu-devel@nongnu.org
Cc: "Daniel P. Berrangé" <berrange@redhat.com>,
	"Michael Tokarev" <mjt@tls.msk.ru>
Subject: Re: [PATCH 0/2] [RfC] edk2: add qemu variable store firmware builds
Date: Fri, 28 Nov 2025 14:05:01 +0100	[thread overview]
Message-ID: <d2870199-cc30-4268-b7ce-1ef9dc5ece16@linaro.org> (raw)
In-Reply-To: <20251128092602.373747-1-kraxel@redhat.com>

Cc'ing Michael and Daniel

On 28/11/25 10:25, Gerd Hoffmann wrote:
> This is somewhat related to the bigger question how we want move forward
> with firmware builds in the qemu repo ...
> 
> qemu got uefi variable store support in version 10.0.  With the pending
> edk2 firmware update (patches are on the list right now) edk2 is new
> enough that support for the qemu variable store is present in the code
> base.  This is a compile time option though, so it needs separate
> firmware images.  This little patch series adds them.
> 
> The big question is if we want go down that route.  The images are not
> essential for qemu itself.  The test cases for the acpi tables use the
> firmware images for the traditional, pflash-based efi variable store
> and can continue to do so.
> 
> So, do we want add them?  For qemu developer / user convenience?  Or
> leave that to linux distributions?  Fedora already ships builds (see
> /usr/share/edk2/*/*qemuvars*).
> 
> take care,
>    Gerd
> 
> Gerd Hoffmann (2):
>    edk2: add qemuvars builds to config
>    edk2: add qemuvars build binaries
> 
>   pc-bios/edk2-aarch64-qemuvars.fd.bz2 | Bin 0 -> 1621714 bytes
>   pc-bios/edk2-x86_64-qemuvars.fd.bz2  | Bin 0 -> 2095693 bytes
>   roms/edk2-build.config               |  37 +++++++++++++++++++++++++++
>   3 files changed, 37 insertions(+)
>   create mode 100644 pc-bios/edk2-aarch64-qemuvars.fd.bz2
>   create mode 100644 pc-bios/edk2-x86_64-qemuvars.fd.bz2
> 



      parent reply	other threads:[~2025-11-28 13:05 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-28  9:25 [PATCH 0/2] [RfC] edk2: add qemu variable store firmware builds Gerd Hoffmann
2025-11-28  9:26 ` [PATCH 1/2] edk2: add qemuvars builds to config Gerd Hoffmann
2025-11-28 13:05 ` Philippe Mathieu-Daudé [this message]

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=d2870199-cc30-4268-b7ce-1ef9dc5ece16@linaro.org \
    --to=philmd@linaro.org \
    --cc=berrange@redhat.com \
    --cc=kraxel@redhat.com \
    --cc=mjt@tls.msk.ru \
    --cc=qemu-devel@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).