From: Laszlo Ersek <lersek@redhat.com>
To: qemu devel list <qemu-devel@nongnu.org>
Cc: "Philippe Mathieu-Daudé" <philmd@redhat.com>
Subject: [Qemu-devel] [PATCH 6/6] pc-bios: update the README file with edk2-stable201905 information
Date: Thu, 6 Jun 2019 15:31:10 +0200 [thread overview]
Message-ID: <20190606133110.13754-7-lersek@redhat.com> (raw)
In-Reply-To: <20190606133110.13754-1-lersek@redhat.com>
Refresh the "pc-bios/README" file with edk2, OpenSSL, and Berkeley
SoftFloat release info, matching the edk2-stable201905 firmware images
added in the previous patch.
Cc: Philippe Mathieu-Daudé <philmd@redhat.com>
Ref: https://bugs.launchpad.net/qemu/+bug/1831477
Signed-off-by: Laszlo Ersek <lersek@redhat.com>
---
pc-bios/README | 14 ++++++++------
1 file changed, 8 insertions(+), 6 deletions(-)
diff --git a/pc-bios/README b/pc-bios/README
index 807d95dd5418..180795a55b8a 100644
--- a/pc-bios/README
+++ b/pc-bios/README
@@ -55,9 +55,11 @@
variable store templates built from the TianoCore community's EFI Development
Kit II project
<https://github.com/tianocore/tianocore.github.io/wiki/EDK-II>. The images
- were built at git tag "edk2-stable201903". The firmware binaries bundle parts
- of the OpenSSL project, at git tag "OpenSSL_1_1_0j" (the OpenSSL tag is a
- function of the edk2 tag). Licensing information is given in
- "edk2-licenses.txt". The image files are described by the JSON documents in
- the "pc-bios/descriptors" directory, which conform to the
- "docs/interop/firmware.json" schema.
+ were built at git tag "edk2-stable201905". The firmware binaries bundle parts
+ of the OpenSSL project, at git tag "OpenSSL_1_1_1b" (the OpenSSL tag is a
+ function of the edk2 tag). Parts of the Berkeley SoftFloat library are
+ bundled as well, at Release 3e plus a subsequent typo fix (commit
+ b64af41c3276f97f0e181920400ee056b9c88037), as an OpenSSL dependency on 32-bit
+ ARM. Licensing information is given in "edk2-licenses.txt". The image files
+ are described by the JSON documents in the "pc-bios/descriptors" directory,
+ which conform to the "docs/interop/firmware.json" schema.
--
2.19.1.3.g30247aa5d201
next prev parent reply other threads:[~2019-06-06 13:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-06 13:31 [Qemu-devel] [PATCH 0/6] update edk2 submodule & binaries to edk2-stable201905 Laszlo Ersek
2019-06-06 13:31 ` [Qemu-devel] [PATCH 1/6] roms/Makefile.edk2: define edk2-stable201905 network feature test macros Laszlo Ersek
2019-06-06 13:31 ` [Qemu-devel] [PATCH 2/6] roms/edk2: update submodule from edk2-stable201903 to edk2-stable201905 Laszlo Ersek
2019-06-06 13:31 ` [Qemu-devel] [PATCH 3/6] roms/Makefile.edk2: remove edk2-stable201903 network feature test macros Laszlo Ersek
2019-06-06 13:31 ` [Qemu-devel] [PATCH 4/6] roms/Makefile.edk2: update input file list for "pc-bios/edk2-licenses.txt" Laszlo Ersek
2019-06-06 13:31 ` [Qemu-devel] [PATCH 5/6] pc-bios: refresh edk2 build artifacts for edk2-stable201905 Laszlo Ersek
2019-06-06 13:31 ` Laszlo Ersek [this message]
2019-06-13 15:12 ` [Qemu-devel] [PATCH 0/6] update edk2 submodule & binaries to edk2-stable201905 Laszlo Ersek
2019-06-13 17:41 ` Philippe Mathieu-Daudé
2019-06-14 19:43 ` Laszlo Ersek
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=20190606133110.13754-7-lersek@redhat.com \
--to=lersek@redhat.com \
--cc=philmd@redhat.com \
--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).