qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Gerd Hoffmann <kraxel@redhat.com>
To: qemu-devel@nongnu.org
Cc: "Philippe Mathieu-Daudé" <philmd@linaro.org>,
	"Gerd Hoffmann" <kraxel@redhat.com>
Subject: [PULL 4/5] roms/efi: use pure 64-bit build for edk2-x86_64-secure-code.fd
Date: Wed, 20 Mar 2024 08:08:47 +0100	[thread overview]
Message-ID: <20240320070851.18933-5-kraxel@redhat.com> (raw)
In-Reply-To: <20240320070851.18933-1-kraxel@redhat.com>

Signed-off-by: Gerd Hoffmann <kraxel@redhat.com>
Message-ID: <20240314115307.628118-5-kraxel@redhat.com>
---
 roms/edk2-build.config | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/roms/edk2-build.config b/roms/edk2-build.config
index ef3eb7beebe7..cc9b21154205 100644
--- a/roms/edk2-build.config
+++ b/roms/edk2-build.config
@@ -70,11 +70,11 @@ cpy1 = FV/OVMF_CODE.fd edk2-x86_64-code.fd
 
 [build.ovmf.x86_64.secure]
 desc = ovmf build (64-bit, secure boot)
-conf = OvmfPkg/OvmfPkgIa32X64.dsc
-arch = IA32 X64
+conf = OvmfPkg/OvmfPkgX64.dsc
+arch = X64
 opts = common
        ovmf.sb.smm
-plat = Ovmf3264
+plat = OvmfX64
 dest = ../pc-bios
 cpy1 = FV/OVMF_CODE.fd edk2-x86_64-secure-code.fd
 
-- 
2.44.0



  parent reply	other threads:[~2024-03-20  7:10 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-20  7:08 [PULL 0/5] Edk2 20240320 patches Gerd Hoffmann
2024-03-20  7:08 ` [PULL 1/5] roms/efi: clean up edk2 build config Gerd Hoffmann
2024-03-20  7:08 ` [PULL 2/5] roms/efi: drop workaround for edk2-stable202308 Gerd Hoffmann
2024-03-20  7:08 ` [PULL 3/5] roms/efi: exclude efi shell from secure boot builds Gerd Hoffmann
2024-03-20  7:08 ` Gerd Hoffmann [this message]
2024-03-20  7:08 ` [PULL 5/5] update edk2 binaries for arm, risc-v and x86 secure boot Gerd Hoffmann
2024-03-20 16:58 ` [PULL 0/5] Edk2 20240320 patches Peter Maydell

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=20240320070851.18933-5-kraxel@redhat.com \
    --to=kraxel@redhat.com \
    --cc=philmd@linaro.org \
    --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).