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: "Michael S. Tsirkin" <mst@redhat.com>,
	Igor Mammedov <imammedo@redhat.com>,
	Ani Sinha <anisinha@redhat.com>,
	qemu-riscv <qemu-riscv@nongnu.org>
Subject: Re: [PATCH 0/8] edk2: update to edk2-stable202511
Date: Wed, 26 Nov 2025 16:11:04 +0100	[thread overview]
Message-ID: <3dcc24da-e905-4a48-853a-46c6b17d849f@linaro.org> (raw)
In-Reply-To: <20251126142116.4077056-1-kraxel@redhat.com>

On 26/11/25 15:21, Gerd Hoffmann wrote:
> Update edk2 firmware images to latest upstream release.
> 
> Noteworthy edk2 upstream change is that 32-bit architectures (ia32 and
> arm) are not supported any more, so the qemu builds of these are removed
> too.

Thanks for doing this work.

>   roms/edk2-build.py                            |  21 +++++++--
>   tests/qtest/bios-tables-test.c                |  28 +++++------
>   pc-bios/descriptors/50-edk2-i386-secure.json  |  34 --------------
>   pc-bios/descriptors/60-edk2-aarch64.json      |   2 +-
>   pc-bios/descriptors/60-edk2-arm.json          |  31 ------------
>   pc-bios/descriptors/60-edk2-i386.json         |  33 -------------
>   pc-bios/descriptors/meson.build               |   3 --
>   pc-bios/edk2-aarch64-code.fd.bz2              | Bin 1565763 -> 1662423 bytes
>   ...m-vars.fd.bz2 => edk2-aarch64-vars.fd.bz2} | Bin
>   pc-bios/edk2-arm-code.fd.bz2                  | Bin 1570311 -> 0 bytes
>   pc-bios/edk2-i386-code.fd.bz2                 | Bin 1780004 -> 0 bytes
>   pc-bios/edk2-i386-secure-code.fd.bz2          | Bin 1858666 -> 0 bytes
>   pc-bios/edk2-i386-vars.fd.bz2                 | Bin 190 -> 0 bytes
>   pc-bios/edk2-loongarch64-code.fd.bz2          | Bin 1148383 -> 1178146 bytes
>   pc-bios/edk2-riscv-code.fd.bz2                | Bin 1296526 -> 1252448 bytes

Since here, could we rename this one as edk2-riscv64-code.fd.bz2 for
coherency and clarity?

>   pc-bios/edk2-x86_64-code.fd.bz2               | Bin 1907255 -> 2138026 bytes
>   pc-bios/edk2-x86_64-microvm.fd.bz2            | Bin 1787244 -> 1996414 bytes
>   pc-bios/edk2-x86_64-secure-code.fd.bz2        | Bin 1962992 -> 2293816 bytes


      parent reply	other threads:[~2025-11-26 15:11 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-26 14:21 [PATCH 0/8] edk2: update to edk2-stable202511 Gerd Hoffmann
2025-11-26 14:21 ` [PATCH 1/8] tests/acpi: enable updates Gerd Hoffmann
2025-11-26 14:21 ` [PATCH 2/8] edk2: update build script Gerd Hoffmann
2025-11-26 14:21 ` [PATCH 3/8] edk2: update submodule to edk2-stable202511 Gerd Hoffmann
2025-11-26 14:21 ` [PATCH 4/8] edk2: drop 32-bit build config (ia32 and arm), update aarch64 vars Gerd Hoffmann
2025-11-26 15:08   ` Philippe Mathieu-Daudé
2025-11-26 14:21 ` [PATCH 7/8] tests/acpi: update expected data files Gerd Hoffmann
2025-11-26 22:28   ` Michael S. Tsirkin
2025-11-26 14:21 ` [PATCH 8/8] tests/acpi: disable updates Gerd Hoffmann
2025-11-26 15:11 ` 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=3dcc24da-e905-4a48-853a-46c6b17d849f@linaro.org \
    --to=philmd@linaro.org \
    --cc=anisinha@redhat.com \
    --cc=imammedo@redhat.com \
    --cc=kraxel@redhat.com \
    --cc=mst@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-riscv@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).