From: Gerd Hoffmann <kraxel@redhat.com>
To: qemu-devel@nongnu.org
Cc: "Gerd Hoffmann" <kraxel@redhat.com>,
"Philippe Mathieu-Daudé" <philmd@linaro.org>,
"Ani Sinha" <ani@anisinha.ca>,
"Igor Mammedov" <imammedo@redhat.com>,
"Michael S. Tsirkin" <mst@redhat.com>
Subject: [PATCH 0/6] edk2: update to 2023-02 stable tag
Date: Thu, 16 Mar 2023 10:54:26 +0100 [thread overview]
Message-ID: <20230316095432.1514080-1-kraxel@redhat.com> (raw)
Turned out to be a bit more complicated than just
"update submodule + binaries, done". One acpi
test case needs a fix to not use too small numa
nodes. So posting this as patch series for
review first.
The patch updating the binaries will probably
not make it to to the list. So for testing the
the branch can be pulled here:
git://git.kraxel.org/qemu edk2-stable202302
Alternatively use "make -C roms efi" to build
locally (needs cross compilers for arm, aarch64
and riscv64).
Gerd Hoffmann (6):
acpi: enable tests/data/acpi updates
bios-tables-test: use 128M numa nodes on aarch64
acpi: disable tests/data/acpi updates
edk2: update submodule to edk2-stable202302
edk2: replace build scripts
edk2: update firmware binaries
roms/edk2-build.py | 380 +++++++++++++++++++++++++
tests/qtest/bios-tables-test.c | 6 +-
pc-bios/README | 4 +-
pc-bios/edk2-aarch64-code.fd.bz2 | Bin 1161290 -> 1508184 bytes
pc-bios/edk2-arm-code.fd.bz2 | Bin 1161845 -> 1483149 bytes
pc-bios/edk2-i386-code.fd.bz2 | Bin 1282120 -> 1695318 bytes
pc-bios/edk2-i386-secure-code.fd.bz2 | Bin 1473677 -> 1922002 bytes
pc-bios/edk2-riscv.fd.bz2 | Bin 0 -> 1096418 bytes
pc-bios/edk2-x86_64-code.fd.bz2 | Bin 1327522 -> 1796544 bytes
pc-bios/edk2-x86_64-microvm.fd.bz2 | Bin 1309407 -> 1697788 bytes
pc-bios/edk2-x86_64-secure-code.fd.bz2 | Bin 1513711 -> 1999841 bytes
roms/Makefile | 29 +-
roms/Makefile.edk2 | 178 ------------
roms/edk2 | 2 +-
roms/edk2-build.config | 124 ++++++++
roms/edk2-build.sh | 55 ----
roms/edk2-funcs.sh | 273 ------------------
tests/data/acpi/virt/SRAT.acpihmatvirt | Bin 240 -> 240 bytes
tests/data/acpi/virt/SSDT.memhp | Bin 1817 -> 1817 bytes
19 files changed, 517 insertions(+), 534 deletions(-)
create mode 100755 roms/edk2-build.py
create mode 100644 pc-bios/edk2-riscv.fd.bz2
delete mode 100644 roms/Makefile.edk2
create mode 100644 roms/edk2-build.config
delete mode 100755 roms/edk2-build.sh
delete mode 100644 roms/edk2-funcs.sh
--
2.39.2
next reply other threads:[~2023-03-16 9:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-16 9:54 Gerd Hoffmann [this message]
2023-03-16 9:54 ` [PATCH 1/6] acpi: enable tests/data/acpi updates Gerd Hoffmann
2023-03-16 9:54 ` [PATCH 2/6] bios-tables-test: use 128M numa nodes on aarch64 Gerd Hoffmann
2023-03-28 12:03 ` Igor Mammedov
2023-03-28 12:09 ` Daniel P. Berrangé
2023-03-28 12:28 ` Igor Mammedov
2023-03-16 9:54 ` [PATCH 3/6] acpi: disable tests/data/acpi updates Gerd Hoffmann
2023-03-16 9:54 ` [PATCH 4/6] edk2: update submodule to edk2-stable202302 Gerd Hoffmann
2023-03-16 10:50 ` Philippe Mathieu-Daudé
2023-03-16 9:54 ` [PATCH 5/6] edk2: replace build scripts Gerd Hoffmann
2023-03-16 9:54 ` [PATCH 6/6] edk2: update firmware binaries Gerd Hoffmann
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=20230316095432.1514080-1-kraxel@redhat.com \
--to=kraxel@redhat.com \
--cc=ani@anisinha.ca \
--cc=imammedo@redhat.com \
--cc=mst@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).