2019-03-15 16:27:02 +00:00
|
|
|
# This package depends on automagic byte compilation
|
|
|
|
|
# https://fedoraproject.org/wiki/Changes/No_more_automagic_Python_bytecompilation_phase_2
|
|
|
|
|
%global _python_bytecompile_extra 1
|
|
|
|
|
|
|
|
|
|
# RPM doesn't detect that code in /usr/share is python3, this forces it
|
|
|
|
|
# https://fedoraproject.org/wiki/Changes/Avoid_usr_bin_python_in_RPM_Build#Python_bytecompilation
|
|
|
|
|
%global __python %{__python3}
|
|
|
|
|
|
2019-07-11 23:42:10 +00:00
|
|
|
|
|
|
|
|
# global edk2_date 20180815
|
|
|
|
|
# global edk2_githash cb5f4f45ce
|
|
|
|
|
|
|
|
|
|
%global edk2_stable_date 201905
|
|
|
|
|
%global edk2_stable_str edk2-stable%{edk2_stable_date}
|
|
|
|
|
%global openssl_version 1.1.1b
|
2018-08-16 19:50:44 +00:00
|
|
|
%global qosb_version 1.1.3
|
2019-07-11 23:42:10 +00:00
|
|
|
%global softfloat_version 20180726-gitb64af41
|
2013-05-02 12:46:06 +00:00
|
|
|
|
2019-03-15 16:27:02 +00:00
|
|
|
|
2019-07-12 16:52:11 +00:00
|
|
|
# enrollment is hanging with stable 201905,
|
|
|
|
|
# so temporarily disable it
|
2019-07-11 23:42:10 +00:00
|
|
|
%global skip_enroll 1
|
2019-07-12 16:52:11 +00:00
|
|
|
|
|
|
|
|
|
2018-04-30 11:57:51 +00:00
|
|
|
%define qosb_testing 0
|
|
|
|
|
|
|
|
|
|
%ifarch x86_64
|
|
|
|
|
%define qosb_testing 1
|
|
|
|
|
%endif
|
2017-11-17 07:49:48 +00:00
|
|
|
%if 0%{?fedora:1}
|
2017-11-13 17:44:20 +00:00
|
|
|
%define cross 1
|
2017-11-17 07:49:48 +00:00
|
|
|
%endif
|
2017-11-13 17:44:20 +00:00
|
|
|
|
|
|
|
|
%ifarch %{ix86} x86_64
|
2017-11-17 07:49:48 +00:00
|
|
|
%if 0%{?fedora:1}
|
2017-11-13 17:44:20 +00:00
|
|
|
%define build_ovmf_ia32 1
|
2017-11-17 07:49:48 +00:00
|
|
|
%endif
|
2017-11-13 17:44:20 +00:00
|
|
|
%ifarch x86_64
|
|
|
|
|
%define build_ovmf_x64 1
|
|
|
|
|
%endif
|
|
|
|
|
%endif
|
|
|
|
|
%ifarch aarch64
|
|
|
|
|
%define build_aavmf_aarch64 1
|
|
|
|
|
%endif
|
|
|
|
|
%ifarch %{arm}
|
|
|
|
|
%define build_aavmf_arm 1
|
|
|
|
|
%endif
|
|
|
|
|
%if 0%{?cross:1}
|
|
|
|
|
%define build_ovmf_x64 1
|
|
|
|
|
%define build_ovmf_ia32 1
|
|
|
|
|
%define build_aavmf_aarch64 1
|
|
|
|
|
%define build_aavmf_arm 1
|
|
|
|
|
%endif
|
|
|
|
|
|
2015-12-29 17:03:01 +00:00
|
|
|
Name: edk2
|
2019-03-15 16:27:02 +00:00
|
|
|
#Version: {edk2_date}git{edk2_githash}
|
2019-07-11 23:42:10 +00:00
|
|
|
# Even though edk2 stable releases are YYYYMM, we need
|
|
|
|
|
# to use YYYMMDD to avoid needing to bump package epoch
|
|
|
|
|
# due to previous 'git' Version:
|
|
|
|
|
Version: %{edk2_stable_date}01stable
|
2019-03-15 16:27:02 +00:00
|
|
|
Release: 1%{dist}
|
2015-12-29 17:03:01 +00:00
|
|
|
Summary: EFI Development Kit II
|
2013-05-02 12:46:06 +00:00
|
|
|
|
2016-04-18 12:16:51 +00:00
|
|
|
License: BSD
|
|
|
|
|
URL: http://www.tianocore.org/edk2/
|
2018-08-16 19:50:44 +00:00
|
|
|
|
|
|
|
|
# Tarball generated from git object update-tarball.sh script
|
2019-03-15 16:27:02 +00:00
|
|
|
#Source0: edk2-{edk2_date}-{edk2_githash}.tar.xz
|
|
|
|
|
Source0: https://github.com/tianocore/edk2/archive/%{edk2_stable_str}.tar.gz#/edk2-%{edk2_stable_str}.tar.gz
|
2016-11-06 20:04:24 +00:00
|
|
|
Source1: openssl-%{openssl_version}-hobbled.tar.xz
|
2017-11-14 15:05:26 +00:00
|
|
|
Source2: ovmf-whitepaper-c770f8c.txt
|
2018-04-30 11:57:51 +00:00
|
|
|
Source3: https://github.com/puiterwijk/qemu-ovmf-secureboot/archive/v%{qosb_version}/qemu-ovmf-secureboot-%{qosb_version}.tar.gz
|
2019-07-11 23:42:10 +00:00
|
|
|
Source4: softfloat-%{softfloat_version}.tar.xz
|
2017-11-14 15:05:26 +00:00
|
|
|
Source10: hobble-openssl
|
|
|
|
|
Source11: build-iso.sh
|
|
|
|
|
Source12: update-tarball.sh
|
|
|
|
|
Source13: openssl-patch-to-tarball.sh
|
2016-11-06 20:04:24 +00:00
|
|
|
|
Ship the JSON firmware "descriptor files"
From version 4.1 (due in August 2019) onwards, QEMU ships the so-called
firmware "descriptor files". These are small JSON files that describe
details about UEFI firmware binaries — such as the fimware binary path,
its architecture, supported machine type, NVRAM template and so forth.
You can see examples of these files from the QEMU upstream Git:
https://git.qemu.org/?p=qemu.git;a=tree;f=pc-bios/descriptors
$> tree descriptors/
descriptors/
├── 50-edk2-i386-secure.json
├── 50-edk2-x86_64-secure.json
├── 60-edk2-aarch64.json
├── 60-edk2-arm.json
├── 60-edk2-i386.json
└── 60-edk2-x86_64.json
QEMU 4.1 itself will ship the above files. However, Fedora needs to
ship these file as part of its EDK2 package.
Why?
----
(1) Quoting (with minor formatting edits) Laszlo Ersek:
Distributions providing their own EDK2 packages would not include
the descriptors from upstream QEMU, even if they otherwise package
QEMU. That's beause the descriptor files in QEMU match the
firmware bundled with QEMU -- but the firmware images in the
distros' own EDK2 packages are different. So, if a distro
provides an EDK2 package, then the same EDK2 package should offer
matching descriptors. QEMU offers descriptors (soon) because QEMU
technically distributes edk2 firmware binaries (soon). [Where
"soon" == QEMU 4.1]
(2) And as Dan Berrangé reminded on IRC:
In Fedora, we need to ship them [the "descriptor files"] as part
of the EDK2 package, because Fedora throws away all the firmware
files that QEMU bundles, because we're [Fedora] required to
rebuild everything from pristine source.
- - -
In this patch:
(*) Use the firmware descriptor files provided by Laszlo (thanks!) in
this comment here:
https://bugzilla.redhat.com/show_bug.cgi?id=1728652#c2 ("RFE: Ship
the JSON firmware "descriptor files" as part of EDK2").
On the double-digit priority prefixes, refer to the rationale here:
https://src.fedoraproject.org/rpms/edk2/pull-request/3#comment-27523
(*) Install the JSON files for the relevant architectures in
`/usr/share/qemu/firmware`, as required by specification[+]. And
make each EDK2 own this directory; multiple RPMs owning the same
directory is no problem.
[+] https://git.qemu.org/?p=qemu.git;a=blob;f=docs/interop/firmware.json
Resolves: rhbz#1728652
Signed-off-by: Kashyap Chamarthy <kchamart@redhat.com>
2019-07-12 09:20:38 +00:00
|
|
|
# Fedora-specific JSON "descriptor files"
|
|
|
|
|
Source14: 40-edk2-ovmf-sb-enrolled.json
|
|
|
|
|
Source15: 50-edk2-ovmf-sb.json
|
|
|
|
|
Source16: 60-edk2-ovmf.json
|
|
|
|
|
Source17: 40-edk2-ovmf-ia32-sb-enrolled.json
|
|
|
|
|
Source18: 50-edk2-ovmf-ia32-sb.json
|
|
|
|
|
Source19: 60-edk2-ovmf-ia32.json
|
|
|
|
|
Source20: 70-edk2-aarch64-verbose.json
|
|
|
|
|
Source21: 70-edk2-arm-verbose.json
|
|
|
|
|
|
2017-11-17 07:49:48 +00:00
|
|
|
# non-upstream patches
|
2016-05-21 13:04:07 +00:00
|
|
|
Patch0001: 0001-OvmfPkg-silence-EFI_D_VERBOSE-0x00400000-in-NvmExpre.patch
|
|
|
|
|
Patch0002: 0002-OvmfPkg-silence-EFI_D_VERBOSE-0x00400000-in-the-DXE-.patch
|
|
|
|
|
Patch0003: 0003-OvmfPkg-enable-DEBUG_VERBOSE.patch
|
|
|
|
|
Patch0004: 0004-OvmfPkg-increase-max-debug-message-length-to-512.patch
|
2018-05-29 21:06:35 +00:00
|
|
|
Patch0005: 0005-advertise-OpenSSL-on-TianoCore-splash-screen-boot-lo.patch
|
|
|
|
|
Patch0006: 0006-OvmfPkg-QemuVideoDxe-enable-debug-messages-in-VbeShi.patch
|
|
|
|
|
Patch0007: 0007-MdeModulePkg-TerminalDxe-add-other-text-resolutions.patch
|
|
|
|
|
Patch0008: 0008-MdeModulePkg-TerminalDxe-set-xterm-resolution-on-mod.patch
|
|
|
|
|
Patch0009: 0009-OvmfPkg-take-PcdResizeXterm-from-the-QEMU-command-li.patch
|
|
|
|
|
Patch0010: 0010-ArmVirtPkg-QemuFwCfgLib-allow-UEFI_DRIVER-client-mod.patch
|
|
|
|
|
Patch0011: 0011-ArmVirtPkg-take-PcdResizeXterm-from-the-QEMU-command.patch
|
|
|
|
|
Patch0012: 0012-OvmfPkg-allow-exclusion-of-the-shell-from-the-firmwa.patch
|
2019-07-11 23:42:10 +00:00
|
|
|
Patch0013: 0013-ArmPlatformPkg-introduce-fixed-PCD-for-early-hello-m.patch
|
|
|
|
|
Patch0014: 0014-ArmPlatformPkg-PrePeiCore-write-early-hello-message-.patch
|
|
|
|
|
Patch0015: 0015-ArmVirtPkg-set-early-hello-message-RH-only.patch
|
|
|
|
|
Patch0016: 0016-Tweak-the-tools_def-to-support-cross-compiling.patch
|
|
|
|
|
|
2018-05-29 21:06:35 +00:00
|
|
|
|
2017-11-13 17:44:20 +00:00
|
|
|
%if 0%{?cross:1}
|
|
|
|
|
%endif
|
2016-04-18 12:16:51 +00:00
|
|
|
|
2017-11-17 07:49:48 +00:00
|
|
|
%if 0%{?fedora:1}
|
2016-04-18 12:16:51 +00:00
|
|
|
#
|
2016-07-08 11:16:59 +00:00
|
|
|
# actual firmware builds support cross-compiling. edk2-tools
|
|
|
|
|
# in theory should build everywhere without much trouble, but
|
2016-04-18 12:16:51 +00:00
|
|
|
# in practice the edk2 build system barfs on archs it doesn't know
|
|
|
|
|
# (such as ppc), so lets limit things to the known-good ones.
|
|
|
|
|
#
|
|
|
|
|
ExclusiveArch: %{ix86} x86_64 %{arm} aarch64
|
2017-11-17 07:49:48 +00:00
|
|
|
%else
|
|
|
|
|
ExclusiveArch: x86_64 aarch64
|
|
|
|
|
%endif
|
2016-04-18 12:16:51 +00:00
|
|
|
|
2018-03-30 13:04:15 +00:00
|
|
|
BuildRequires: gcc gcc-c++
|
2019-03-15 16:27:02 +00:00
|
|
|
BuildRequires: python3 python3-devel
|
2015-12-29 17:03:01 +00:00
|
|
|
BuildRequires: libuuid-devel
|
2017-11-13 17:44:20 +00:00
|
|
|
%if 0%{?cross:1}
|
2016-05-21 14:39:41 +00:00
|
|
|
BuildRequires: gcc-aarch64-linux-gnu
|
2016-07-21 21:47:43 +00:00
|
|
|
BuildRequires: gcc-arm-linux-gnu
|
2016-07-08 11:16:59 +00:00
|
|
|
BuildRequires: gcc-x86_64-linux-gnu
|
2017-11-13 17:44:20 +00:00
|
|
|
%endif
|
2016-04-18 12:16:51 +00:00
|
|
|
BuildRequires: iasl
|
|
|
|
|
BuildRequires: nasm
|
2018-03-08 10:38:21 +00:00
|
|
|
BuildRequires: qemu-img
|
2016-04-18 12:16:51 +00:00
|
|
|
BuildRequires: genisoimage
|
2019-03-15 16:27:02 +00:00
|
|
|
BuildRequires: bc
|
2013-05-02 12:46:06 +00:00
|
|
|
|
2018-04-30 11:57:51 +00:00
|
|
|
# These are for QOSB
|
|
|
|
|
BuildRequires: python3-requests
|
2018-04-30 15:43:54 +00:00
|
|
|
BuildRequires: qemu-system-x86
|
2018-04-30 11:57:51 +00:00
|
|
|
%if %{?qosb_testing}
|
|
|
|
|
# This is used for testing the enrollment: builds are run in a chroot, lacking
|
|
|
|
|
# a kernel. The testing is only performed on x86_64 for now, but we can't make
|
|
|
|
|
# the BuildRequires only on a specific arch, as that'd come through in the SRPM
|
|
|
|
|
# NOTE: The actual enrollment needs to happen in all builds for all architectures,
|
|
|
|
|
# because OVMF is built as noarch, which means that koji enforces that the build
|
|
|
|
|
# results don't actually differ per arch, and then it picks a random arches' build
|
|
|
|
|
# for the actual RPM.
|
|
|
|
|
BuildRequires: kernel-core
|
|
|
|
|
%endif
|
2016-05-21 14:39:41 +00:00
|
|
|
|
2013-05-02 12:46:06 +00:00
|
|
|
%description
|
2013-08-22 10:46:29 +00:00
|
|
|
EDK II is a development code base for creating UEFI drivers, applications
|
|
|
|
|
and firmware images.
|
2013-05-02 12:46:06 +00:00
|
|
|
|
|
|
|
|
%package tools
|
2015-12-29 17:03:01 +00:00
|
|
|
Summary: EFI Development Kit II Tools
|
2013-05-02 12:46:06 +00:00
|
|
|
%description tools
|
|
|
|
|
This package provides tools that are needed to
|
|
|
|
|
build EFI executables and ROMs using the GNU tools.
|
|
|
|
|
|
|
|
|
|
%package tools-python
|
2015-12-29 17:03:01 +00:00
|
|
|
Summary: EFI Development Kit II Tools
|
2019-03-15 16:27:02 +00:00
|
|
|
Requires: python3
|
2013-05-02 12:46:06 +00:00
|
|
|
BuildArch: noarch
|
|
|
|
|
|
|
|
|
|
%description tools-python
|
|
|
|
|
This package provides tools that are needed to build EFI executables
|
|
|
|
|
and ROMs using the GNU tools. You do not need to install this package;
|
|
|
|
|
you probably want to install edk2-tools only.
|
|
|
|
|
|
|
|
|
|
%package tools-doc
|
2015-12-29 17:03:01 +00:00
|
|
|
Summary: Documentation for EFI Development Kit II Tools
|
2016-04-18 12:16:51 +00:00
|
|
|
BuildArch: noarch
|
2013-05-02 12:46:06 +00:00
|
|
|
%description tools-doc
|
|
|
|
|
This package documents the tools that are needed to
|
|
|
|
|
build EFI executables and ROMs using the GNU tools.
|
|
|
|
|
|
2018-04-30 11:57:51 +00:00
|
|
|
%package qosb
|
|
|
|
|
Summary: Tool to enroll secureboot
|
2018-11-14 16:10:37 +00:00
|
|
|
Requires: python3
|
2018-04-30 11:57:51 +00:00
|
|
|
Buildarch: noarch
|
|
|
|
|
%description qosb
|
|
|
|
|
This package contains QOSB (QEMU OVMF Secure Boot), which can enroll OVMF
|
|
|
|
|
variable files to enforce Secure Boot.
|
|
|
|
|
|
|
|
|
|
|
2017-11-13 17:44:20 +00:00
|
|
|
%if 0%{?build_ovmf_x64:1}
|
2016-04-18 12:16:51 +00:00
|
|
|
%package ovmf
|
|
|
|
|
Summary: Open Virtual Machine Firmware
|
2018-07-18 14:33:51 +00:00
|
|
|
# OVMF includes the Secure Boot and IPv6 features; it has a builtin OpenSSL
|
|
|
|
|
# library.
|
2016-04-18 12:16:51 +00:00
|
|
|
License: BSD and OpenSSL
|
2018-07-23 08:57:29 +00:00
|
|
|
Provides: bundled(openssl)
|
2017-11-13 17:44:20 +00:00
|
|
|
Provides: OVMF = %{version}-%{release}
|
|
|
|
|
Obsoletes: OVMF < %{version}-%{release}
|
2016-04-18 12:16:51 +00:00
|
|
|
BuildArch: noarch
|
|
|
|
|
%description ovmf
|
|
|
|
|
EFI Development Kit II
|
|
|
|
|
Open Virtual Machine Firmware (x64)
|
2017-11-13 17:44:20 +00:00
|
|
|
%endif
|
2016-04-18 12:16:51 +00:00
|
|
|
|
2017-11-13 17:44:20 +00:00
|
|
|
%if 0%{?build_ovmf_ia32:1}
|
2017-03-15 21:56:49 +00:00
|
|
|
%package ovmf-ia32
|
|
|
|
|
Summary: Open Virtual Machine Firmware
|
2018-07-18 14:33:51 +00:00
|
|
|
# OVMF includes the Secure Boot and IPv6 features; it has a builtin OpenSSL
|
|
|
|
|
# library.
|
2017-03-15 21:56:49 +00:00
|
|
|
License: BSD and OpenSSL
|
2018-07-23 08:57:29 +00:00
|
|
|
Provides: bundled(openssl)
|
2017-03-15 21:56:49 +00:00
|
|
|
BuildArch: noarch
|
|
|
|
|
%description ovmf-ia32
|
|
|
|
|
EFI Development Kit II
|
|
|
|
|
Open Virtual Machine Firmware (ia32)
|
2017-11-13 17:44:20 +00:00
|
|
|
%endif
|
2017-03-15 21:56:49 +00:00
|
|
|
|
2017-11-13 17:44:20 +00:00
|
|
|
%if 0%{?build_aavmf_aarch64:1}
|
2016-04-18 12:16:51 +00:00
|
|
|
%package aarch64
|
|
|
|
|
Summary: AARCH64 Virtual Machine Firmware
|
2017-11-13 17:44:20 +00:00
|
|
|
Provides: AAVMF = %{version}-%{release}
|
|
|
|
|
Obsoletes: AAVMF < %{version}-%{release}
|
2016-04-18 12:16:51 +00:00
|
|
|
BuildArch: noarch
|
2018-07-18 14:33:51 +00:00
|
|
|
# No Secure Boot for AAVMF yet, but we include OpenSSL for the IPv6 stack.
|
|
|
|
|
License: BSD and OpenSSL
|
2018-07-23 08:57:29 +00:00
|
|
|
Provides: bundled(openssl)
|
2016-04-18 12:16:51 +00:00
|
|
|
%description aarch64
|
|
|
|
|
EFI Development Kit II
|
|
|
|
|
AARCH64 UEFI Firmware
|
2017-11-13 17:44:20 +00:00
|
|
|
%endif
|
2016-05-21 14:39:41 +00:00
|
|
|
|
2017-11-13 17:44:20 +00:00
|
|
|
%if 0%{?build_aavmf_arm:1}
|
2016-07-21 21:47:43 +00:00
|
|
|
%package arm
|
|
|
|
|
Summary: ARM Virtual Machine Firmware
|
|
|
|
|
BuildArch: noarch
|
|
|
|
|
%description arm
|
|
|
|
|
EFI Development Kit II
|
|
|
|
|
armv7 UEFI Firmware
|
2017-11-13 17:44:20 +00:00
|
|
|
%endif
|
2016-07-21 21:47:43 +00:00
|
|
|
|
2016-04-18 12:16:51 +00:00
|
|
|
|
2013-05-02 12:46:06 +00:00
|
|
|
%prep
|
2019-03-15 16:27:02 +00:00
|
|
|
%setup -q -n edk2-%{edk2_stable_str}
|
2016-04-18 12:16:51 +00:00
|
|
|
|
2017-11-14 15:05:26 +00:00
|
|
|
# Ensure old shell and binary packages are not used
|
|
|
|
|
rm -rf EdkShellBinPkg
|
|
|
|
|
rm -rf EdkShellPkg
|
|
|
|
|
rm -rf FatBinPkg
|
|
|
|
|
rm -rf ShellBinPkg
|
|
|
|
|
|
2018-08-16 19:50:44 +00:00
|
|
|
# copy whitepaper into place
|
2017-11-14 15:05:26 +00:00
|
|
|
cp -a -- %{SOURCE2} .
|
2018-08-16 19:50:44 +00:00
|
|
|
# extract openssl into place
|
2019-03-15 16:27:02 +00:00
|
|
|
tar -xvf %{SOURCE1} --strip-components=1 --directory CryptoPkg/Library/OpensslLib/openssl
|
2019-07-11 23:42:10 +00:00
|
|
|
# extract softfloat into place
|
|
|
|
|
tar -xvf %{SOURCE4} --strip-components=1 --directory ArmPkg/Library/ArmSoftFloatLib/berkeley-softfloat-3/
|
2018-01-19 08:36:03 +00:00
|
|
|
|
2018-04-30 11:57:51 +00:00
|
|
|
# Extract QOSB
|
|
|
|
|
tar -xvf %{SOURCE3}
|
|
|
|
|
mv qemu-ovmf-secureboot-%{qosb_version}/README.md README.qosb
|
|
|
|
|
mv qemu-ovmf-secureboot-%{qosb_version}/LICENSE LICENSE.qosb
|
|
|
|
|
|
2018-01-19 08:36:03 +00:00
|
|
|
%autopatch -p1
|
2017-11-14 15:05:26 +00:00
|
|
|
base64 --decode < MdeModulePkg/Logo/Logo-OpenSSL.bmp.b64 > MdeModulePkg/Logo/Logo-OpenSSL.bmp
|
2016-05-21 14:39:41 +00:00
|
|
|
|
2019-07-11 23:42:10 +00:00
|
|
|
|
|
|
|
|
|
2016-04-18 12:16:51 +00:00
|
|
|
%build
|
|
|
|
|
source ./edksetup.sh
|
|
|
|
|
|
2016-05-13 19:39:35 +00:00
|
|
|
# compiler
|
2018-07-18 14:33:51 +00:00
|
|
|
CC_FLAGS="-t GCC5"
|
2016-04-18 12:16:51 +00:00
|
|
|
|
|
|
|
|
# parallel builds
|
|
|
|
|
JOBS="%{?_smp_mflags}"
|
|
|
|
|
JOBS="${JOBS#-j}"
|
|
|
|
|
if test "$JOBS" != ""; then
|
|
|
|
|
CC_FLAGS="${CC_FLAGS} -n $JOBS"
|
|
|
|
|
fi
|
|
|
|
|
|
|
|
|
|
# common features
|
2019-07-11 23:42:10 +00:00
|
|
|
CC_FLAGS="$CC_FLAGS --cmd-len=65536 -b DEBUG --hash"
|
2018-07-18 14:33:51 +00:00
|
|
|
CC_FLAGS="$CC_FLAGS -D NETWORK_IP6_ENABLE"
|
2018-08-22 23:03:42 +00:00
|
|
|
CC_FLAGS="$CC_FLAGS -D TPM2_ENABLE"
|
2016-04-18 12:16:51 +00:00
|
|
|
|
|
|
|
|
# ovmf features
|
|
|
|
|
OVMF_FLAGS="${CC_FLAGS}"
|
2018-01-19 08:36:03 +00:00
|
|
|
OVMF_FLAGS="${OVMF_FLAGS} -D TLS_ENABLE"
|
2016-04-18 12:16:51 +00:00
|
|
|
OVMF_FLAGS="${OVMF_FLAGS} -D HTTP_BOOT_ENABLE"
|
|
|
|
|
OVMF_FLAGS="${OVMF_FLAGS} -D NETWORK_IP6_ENABLE"
|
2017-05-09 17:03:58 +00:00
|
|
|
OVMF_FLAGS="${OVMF_FLAGS} -D FD_SIZE_2MB"
|
2016-04-18 12:16:51 +00:00
|
|
|
|
|
|
|
|
# ovmf + secure boot features
|
|
|
|
|
OVMF_SB_FLAGS="${OVMF_FLAGS}"
|
|
|
|
|
OVMF_SB_FLAGS="${OVMF_SB_FLAGS} -D SECURE_BOOT_ENABLE"
|
|
|
|
|
OVMF_SB_FLAGS="${OVMF_SB_FLAGS} -D SMM_REQUIRE"
|
|
|
|
|
OVMF_SB_FLAGS="${OVMF_SB_FLAGS} -D EXCLUDE_SHELL_FROM_FD"
|
|
|
|
|
|
|
|
|
|
# arm firmware features
|
|
|
|
|
ARM_FLAGS="${CC_FLAGS}"
|
|
|
|
|
ARM_FLAGS="${ARM_FLAGS} -D DEBUG_PRINT_ERROR_LEVEL=0x8040004F"
|
|
|
|
|
|
2016-05-21 14:39:41 +00:00
|
|
|
unset MAKEFLAGS
|
2018-08-31 17:07:49 +00:00
|
|
|
make -C BaseTools %{?_smp_mflags} \
|
|
|
|
|
EXTRA_OPTFLAGS="%{optflags}" \
|
|
|
|
|
EXTRA_LDFLAGS="%{__global_ldflags}"
|
2016-04-18 13:53:38 +00:00
|
|
|
sed -i -e 's/-Werror//' Conf/tools_def.txt
|
2016-04-18 12:16:51 +00:00
|
|
|
|
2017-03-15 21:56:49 +00:00
|
|
|
|
2017-11-13 17:44:20 +00:00
|
|
|
%if 0%{?cross:1}
|
2018-07-18 14:33:51 +00:00
|
|
|
export GCC5_IA32_PREFIX="x86_64-linux-gnu-"
|
|
|
|
|
export GCC5_X64_PREFIX="x86_64-linux-gnu-"
|
|
|
|
|
export GCC5_AARCH64_PREFIX="aarch64-linux-gnu-"
|
|
|
|
|
export GCC5_ARM_PREFIX="arm-linux-gnu-"
|
2017-11-13 17:44:20 +00:00
|
|
|
%endif
|
|
|
|
|
|
|
|
|
|
# build ovmf (x64)
|
|
|
|
|
%if 0%{?build_ovmf_x64:1}
|
2016-04-18 12:16:51 +00:00
|
|
|
mkdir -p ovmf
|
|
|
|
|
build ${OVMF_FLAGS} -a X64 -p OvmfPkg/OvmfPkgX64.dsc
|
2017-03-15 21:56:49 +00:00
|
|
|
cp Build/OvmfX64/*/FV/OVMF_*.fd ovmf/
|
2016-04-18 12:16:51 +00:00
|
|
|
rm -rf Build/OvmfX64
|
|
|
|
|
|
2017-03-15 21:56:49 +00:00
|
|
|
# build ovmf (x64) with secure boot
|
2016-04-18 12:16:51 +00:00
|
|
|
build ${OVMF_SB_FLAGS} -a IA32 -a X64 -p OvmfPkg/OvmfPkgIa32X64.dsc
|
|
|
|
|
cp Build/Ovmf3264/*/FV/OVMF_CODE.fd ovmf/OVMF_CODE.secboot.fd
|
|
|
|
|
|
2017-03-15 21:56:49 +00:00
|
|
|
# build ovmf (x64) shell iso with EnrollDefaultKeys
|
|
|
|
|
cp Build/Ovmf3264/*/X64/Shell.efi ovmf/
|
2016-04-18 12:16:51 +00:00
|
|
|
cp Build/Ovmf3264/*/X64/EnrollDefaultKeys.efi ovmf
|
2017-03-15 21:56:49 +00:00
|
|
|
sh %{_sourcedir}/build-iso.sh ovmf/
|
2018-04-30 11:57:51 +00:00
|
|
|
|
2019-07-11 23:42:10 +00:00
|
|
|
%if !%{skip_enroll}
|
2018-04-30 11:57:51 +00:00
|
|
|
python3 qemu-ovmf-secureboot-%{qosb_version}/ovmf-vars-generator \
|
2019-07-11 23:42:10 +00:00
|
|
|
--qemu-binary /usr/bin/qemu-system-x86_64 \
|
|
|
|
|
--ovmf-binary ovmf/OVMF_CODE.secboot.fd \
|
|
|
|
|
--ovmf-template-vars ovmf/OVMF_VARS.fd \
|
|
|
|
|
--uefi-shell-iso ovmf/UefiShell.iso \
|
|
|
|
|
--skip-testing \
|
|
|
|
|
ovmf/OVMF_VARS.secboot.fd
|
|
|
|
|
%endif
|
2017-11-13 17:44:20 +00:00
|
|
|
%endif
|
2016-04-18 12:16:51 +00:00
|
|
|
|
2017-03-15 21:56:49 +00:00
|
|
|
|
|
|
|
|
# build ovmf-ia32
|
2017-11-13 17:44:20 +00:00
|
|
|
%if 0%{?build_ovmf_ia32:1}
|
2017-03-15 21:56:49 +00:00
|
|
|
mkdir -p ovmf-ia32
|
|
|
|
|
build ${OVMF_FLAGS} -a IA32 -p OvmfPkg/OvmfPkgIa32.dsc
|
2019-07-12 18:08:23 +00:00
|
|
|
cp Build/OvmfIa32/*/FV/OVMF_CODE*.fd ovmf-ia32/
|
|
|
|
|
# cp VARS files from from ovmf/, which are all we need
|
|
|
|
|
cp ovmf/OVMF_VARS*.fd ovmf-ia32/
|
2017-03-15 21:56:49 +00:00
|
|
|
rm -rf Build/OvmfIa32
|
|
|
|
|
|
|
|
|
|
# build ovmf-ia32 with secure boot
|
|
|
|
|
build ${OVMF_SB_FLAGS} -a IA32 -p OvmfPkg/OvmfPkgIa32.dsc
|
|
|
|
|
cp Build/OvmfIa32/*/FV/OVMF_CODE.fd ovmf-ia32/OVMF_CODE.secboot.fd
|
|
|
|
|
|
|
|
|
|
# build ovmf-ia32 shell iso with EnrollDefaultKeys
|
|
|
|
|
cp Build/OvmfIa32/*/IA32/Shell.efi ovmf-ia32/Shell.efi
|
|
|
|
|
cp Build/OvmfIa32/*/IA32/EnrollDefaultKeys.efi ovmf-ia32/EnrollDefaultKeys.efi
|
|
|
|
|
sh %{_sourcedir}/build-iso.sh ovmf-ia32/
|
2017-11-13 17:44:20 +00:00
|
|
|
%endif
|
2017-03-15 21:56:49 +00:00
|
|
|
|
|
|
|
|
|
2016-07-21 21:47:43 +00:00
|
|
|
# build aarch64 firmware
|
2017-11-13 17:44:20 +00:00
|
|
|
%if 0%{?build_aavmf_aarch64:1}
|
2016-04-18 12:16:51 +00:00
|
|
|
mkdir -p aarch64
|
|
|
|
|
build $ARM_FLAGS -a AARCH64 -p ArmVirtPkg/ArmVirtQemu.dsc
|
|
|
|
|
cp Build/ArmVirtQemu-AARCH64/DEBUG_*/FV/*.fd aarch64
|
|
|
|
|
dd of="aarch64/QEMU_EFI-pflash.raw" if="/dev/zero" bs=1M count=64
|
|
|
|
|
dd of="aarch64/QEMU_EFI-pflash.raw" if="aarch64/QEMU_EFI.fd" conv=notrunc
|
|
|
|
|
dd of="aarch64/vars-template-pflash.raw" if="/dev/zero" bs=1M count=64
|
2017-11-13 17:44:20 +00:00
|
|
|
%endif
|
2016-05-21 14:39:41 +00:00
|
|
|
|
2017-03-15 21:56:49 +00:00
|
|
|
|
2016-07-21 21:47:43 +00:00
|
|
|
# build aarch64 firmware
|
2017-11-13 17:44:20 +00:00
|
|
|
%if 0%{?build_aavmf_arm:1}
|
2016-07-21 21:47:43 +00:00
|
|
|
mkdir -p arm
|
|
|
|
|
build $ARM_FLAGS -a ARM -p ArmVirtPkg/ArmVirtQemu.dsc
|
|
|
|
|
cp Build/ArmVirtQemu-ARM/DEBUG_*/FV/*.fd arm
|
|
|
|
|
dd of="arm/QEMU_EFI-pflash.raw" if="/dev/zero" bs=1M count=64
|
|
|
|
|
dd of="arm/QEMU_EFI-pflash.raw" if="arm/QEMU_EFI.fd" conv=notrunc
|
|
|
|
|
dd of="arm/vars-template-pflash.raw" if="/dev/zero" bs=1M count=64
|
2017-11-13 17:44:20 +00:00
|
|
|
%endif
|
2013-05-02 12:46:06 +00:00
|
|
|
|
2019-07-11 23:42:10 +00:00
|
|
|
|
|
|
|
|
|
2018-04-30 11:57:51 +00:00
|
|
|
%check
|
|
|
|
|
%if 0%{?build_ovmf_x64:1}
|
|
|
|
|
%if 0%{?qosb_testing}
|
2019-07-11 23:42:10 +00:00
|
|
|
%if !%{skip_enroll}
|
2018-04-30 11:57:51 +00:00
|
|
|
python3 qemu-ovmf-secureboot-%{qosb_version}/ovmf-vars-generator \
|
2019-07-11 23:42:10 +00:00
|
|
|
--qemu-binary /usr/bin/qemu-system-x86_64 \
|
|
|
|
|
--ovmf-binary ovmf/OVMF_CODE.secboot.fd \
|
|
|
|
|
--ovmf-template-vars ovmf/OVMF_VARS.fd \
|
|
|
|
|
--uefi-shell-iso ovmf/UefiShell.iso \
|
|
|
|
|
--skip-enrollment \
|
|
|
|
|
--print-output \
|
|
|
|
|
--no-download \
|
|
|
|
|
--kernel-path `rpm -ql kernel-core | grep "\/vmlinuz$" -m 1` \
|
|
|
|
|
ovmf/OVMF_VARS.secboot.fd
|
2018-04-30 11:57:51 +00:00
|
|
|
%endif
|
|
|
|
|
%endif
|
2019-07-11 23:42:10 +00:00
|
|
|
%endif
|
|
|
|
|
|
|
|
|
|
|
2018-04-30 11:57:51 +00:00
|
|
|
|
2013-05-02 12:46:06 +00:00
|
|
|
%install
|
2018-07-18 14:33:51 +00:00
|
|
|
cp CryptoPkg/Library/OpensslLib/openssl/LICENSE LICENSE.openssl
|
2016-04-18 12:16:51 +00:00
|
|
|
mkdir -p %{buildroot}%{_bindir} \
|
|
|
|
|
%{buildroot}%{_datadir}/%{name}/Conf \
|
|
|
|
|
%{buildroot}%{_datadir}/%{name}/Scripts
|
|
|
|
|
install BaseTools/Source/C/bin/* \
|
2015-12-29 17:03:01 +00:00
|
|
|
%{buildroot}%{_bindir}
|
2016-04-18 12:16:51 +00:00
|
|
|
install BaseTools/BinWrappers/PosixLike/LzmaF86Compress \
|
|
|
|
|
%{buildroot}%{_bindir}
|
|
|
|
|
install BaseTools/BuildEnv \
|
2014-06-24 07:50:13 +00:00
|
|
|
%{buildroot}%{_datadir}/%{name}
|
2016-04-18 12:16:51 +00:00
|
|
|
install BaseTools/Conf/*.template \
|
2014-06-23 15:25:24 +00:00
|
|
|
%{buildroot}%{_datadir}/%{name}/Conf
|
2016-04-18 12:16:51 +00:00
|
|
|
install BaseTools/Scripts/GccBase.lds \
|
2014-06-23 15:25:24 +00:00
|
|
|
%{buildroot}%{_datadir}/%{name}/Scripts
|
|
|
|
|
|
2016-04-18 12:16:51 +00:00
|
|
|
cp -R BaseTools/Source/Python %{buildroot}%{_datadir}/%{name}/Python
|
2014-06-23 15:25:24 +00:00
|
|
|
for i in build BPDG Ecc GenDepex GenFds GenPatchPcdTable PatchPcdValue TargetTool Trim UPT; do
|
2016-04-18 12:16:51 +00:00
|
|
|
echo '#!/bin/sh
|
|
|
|
|
export PYTHONPATH=%{_datadir}/%{name}/Python
|
2019-03-15 16:27:02 +00:00
|
|
|
exec python3 '%{_datadir}/%{name}/Python/$i/$i.py' "$@"' > %{buildroot}%{_bindir}/$i
|
2013-05-02 12:46:06 +00:00
|
|
|
chmod +x %{buildroot}%{_bindir}/$i
|
|
|
|
|
done
|
|
|
|
|
|
2016-04-18 12:16:51 +00:00
|
|
|
mkdir -p %{buildroot}/usr/share/%{name}
|
2017-11-13 17:44:20 +00:00
|
|
|
%if 0%{?build_ovmf_x64:1}
|
2016-04-18 12:16:51 +00:00
|
|
|
cp -a ovmf %{buildroot}/usr/share/%{name}
|
2017-11-13 17:44:20 +00:00
|
|
|
# Libvirt hardcodes this directory name
|
|
|
|
|
mkdir %{buildroot}/usr/share/OVMF
|
|
|
|
|
ln -sf ../%{name}/ovmf/OVMF_CODE.fd %{buildroot}/usr/share/OVMF
|
|
|
|
|
ln -sf ../%{name}/ovmf/OVMF_CODE.secboot.fd %{buildroot}/usr/share/OVMF
|
2017-11-14 16:50:12 +00:00
|
|
|
ln -sf ../%{name}/ovmf/OVMF_VARS.fd %{buildroot}/usr/share/OVMF
|
2018-04-30 11:57:51 +00:00
|
|
|
ln -sf ../%{name}/ovmf/OVMF_VARS.secboot.fd %{buildroot}/usr/share/OVMF
|
2017-11-13 17:44:20 +00:00
|
|
|
ln -sf ../%{name}/ovmf/UefiShell.iso %{buildroot}/usr/share/OVMF
|
Ship the JSON firmware "descriptor files"
From version 4.1 (due in August 2019) onwards, QEMU ships the so-called
firmware "descriptor files". These are small JSON files that describe
details about UEFI firmware binaries — such as the fimware binary path,
its architecture, supported machine type, NVRAM template and so forth.
You can see examples of these files from the QEMU upstream Git:
https://git.qemu.org/?p=qemu.git;a=tree;f=pc-bios/descriptors
$> tree descriptors/
descriptors/
├── 50-edk2-i386-secure.json
├── 50-edk2-x86_64-secure.json
├── 60-edk2-aarch64.json
├── 60-edk2-arm.json
├── 60-edk2-i386.json
└── 60-edk2-x86_64.json
QEMU 4.1 itself will ship the above files. However, Fedora needs to
ship these file as part of its EDK2 package.
Why?
----
(1) Quoting (with minor formatting edits) Laszlo Ersek:
Distributions providing their own EDK2 packages would not include
the descriptors from upstream QEMU, even if they otherwise package
QEMU. That's beause the descriptor files in QEMU match the
firmware bundled with QEMU -- but the firmware images in the
distros' own EDK2 packages are different. So, if a distro
provides an EDK2 package, then the same EDK2 package should offer
matching descriptors. QEMU offers descriptors (soon) because QEMU
technically distributes edk2 firmware binaries (soon). [Where
"soon" == QEMU 4.1]
(2) And as Dan Berrangé reminded on IRC:
In Fedora, we need to ship them [the "descriptor files"] as part
of the EDK2 package, because Fedora throws away all the firmware
files that QEMU bundles, because we're [Fedora] required to
rebuild everything from pristine source.
- - -
In this patch:
(*) Use the firmware descriptor files provided by Laszlo (thanks!) in
this comment here:
https://bugzilla.redhat.com/show_bug.cgi?id=1728652#c2 ("RFE: Ship
the JSON firmware "descriptor files" as part of EDK2").
On the double-digit priority prefixes, refer to the rationale here:
https://src.fedoraproject.org/rpms/edk2/pull-request/3#comment-27523
(*) Install the JSON files for the relevant architectures in
`/usr/share/qemu/firmware`, as required by specification[+]. And
make each EDK2 own this directory; multiple RPMs owning the same
directory is no problem.
[+] https://git.qemu.org/?p=qemu.git;a=blob;f=docs/interop/firmware.json
Resolves: rhbz#1728652
Signed-off-by: Kashyap Chamarthy <kchamart@redhat.com>
2019-07-12 09:20:38 +00:00
|
|
|
|
|
|
|
|
# For distro-provided firmware packages, the specification
|
|
|
|
|
# (https://git.qemu.org/?p=qemu.git;a=blob;f=docs/interop/firmware.json)
|
|
|
|
|
# says the JSON "descriptor files" to be searched in this directory:
|
|
|
|
|
# `/usr/share/firmware/`. Create it.
|
|
|
|
|
mkdir -p %{buildroot}/%{_datadir}/qemu/firmware
|
|
|
|
|
|
|
|
|
|
# Install the two variants of the x86_64 firmware descriptor files
|
|
|
|
|
# (50-edk2-x86_64-secure.json and 60-edk2-x86_64.json)
|
|
|
|
|
install -pm 644 %{SOURCE14} %{buildroot}/%{_datadir}/qemu/firmware
|
|
|
|
|
install -pm 644 %{SOURCE15} %{buildroot}/%{_datadir}/qemu/firmware
|
|
|
|
|
install -pm 644 %{SOURCE16} %{buildroot}/%{_datadir}/qemu/firmware
|
2017-11-13 17:44:20 +00:00
|
|
|
%endif
|
|
|
|
|
%if 0%{?build_ovmf_ia32:1}
|
2017-03-15 21:56:49 +00:00
|
|
|
cp -a ovmf-ia32 %{buildroot}/usr/share/%{name}
|
Ship the JSON firmware "descriptor files"
From version 4.1 (due in August 2019) onwards, QEMU ships the so-called
firmware "descriptor files". These are small JSON files that describe
details about UEFI firmware binaries — such as the fimware binary path,
its architecture, supported machine type, NVRAM template and so forth.
You can see examples of these files from the QEMU upstream Git:
https://git.qemu.org/?p=qemu.git;a=tree;f=pc-bios/descriptors
$> tree descriptors/
descriptors/
├── 50-edk2-i386-secure.json
├── 50-edk2-x86_64-secure.json
├── 60-edk2-aarch64.json
├── 60-edk2-arm.json
├── 60-edk2-i386.json
└── 60-edk2-x86_64.json
QEMU 4.1 itself will ship the above files. However, Fedora needs to
ship these file as part of its EDK2 package.
Why?
----
(1) Quoting (with minor formatting edits) Laszlo Ersek:
Distributions providing their own EDK2 packages would not include
the descriptors from upstream QEMU, even if they otherwise package
QEMU. That's beause the descriptor files in QEMU match the
firmware bundled with QEMU -- but the firmware images in the
distros' own EDK2 packages are different. So, if a distro
provides an EDK2 package, then the same EDK2 package should offer
matching descriptors. QEMU offers descriptors (soon) because QEMU
technically distributes edk2 firmware binaries (soon). [Where
"soon" == QEMU 4.1]
(2) And as Dan Berrangé reminded on IRC:
In Fedora, we need to ship them [the "descriptor files"] as part
of the EDK2 package, because Fedora throws away all the firmware
files that QEMU bundles, because we're [Fedora] required to
rebuild everything from pristine source.
- - -
In this patch:
(*) Use the firmware descriptor files provided by Laszlo (thanks!) in
this comment here:
https://bugzilla.redhat.com/show_bug.cgi?id=1728652#c2 ("RFE: Ship
the JSON firmware "descriptor files" as part of EDK2").
On the double-digit priority prefixes, refer to the rationale here:
https://src.fedoraproject.org/rpms/edk2/pull-request/3#comment-27523
(*) Install the JSON files for the relevant architectures in
`/usr/share/qemu/firmware`, as required by specification[+]. And
make each EDK2 own this directory; multiple RPMs owning the same
directory is no problem.
[+] https://git.qemu.org/?p=qemu.git;a=blob;f=docs/interop/firmware.json
Resolves: rhbz#1728652
Signed-off-by: Kashyap Chamarthy <kchamart@redhat.com>
2019-07-12 09:20:38 +00:00
|
|
|
|
|
|
|
|
# Install the two variants of the ia32 firmware descriptor files
|
|
|
|
|
# (50-edk2-i386-secure.json and 60-edk2-i386.json)
|
|
|
|
|
install -pm 644 %{SOURCE17} %{buildroot}/%{_datadir}/qemu/firmware
|
|
|
|
|
install -pm 644 %{SOURCE18} %{buildroot}/%{_datadir}/qemu/firmware
|
|
|
|
|
install -pm 644 %{SOURCE19} %{buildroot}/%{_datadir}/qemu/firmware
|
2017-11-13 17:44:20 +00:00
|
|
|
%endif
|
|
|
|
|
%if 0%{?build_aavmf_aarch64:1}
|
2016-04-18 12:16:51 +00:00
|
|
|
cp -a aarch64 %{buildroot}/usr/share/%{name}
|
2017-11-13 17:44:20 +00:00
|
|
|
# Libvirt hardcodes this directory name
|
|
|
|
|
mkdir %{buildroot}/usr/share/AAVMF
|
|
|
|
|
ln -sf ../%{name}/aarch64/QEMU_EFI-pflash.raw %{buildroot}/usr/share/AAVMF/AAVMF_CODE.fd
|
|
|
|
|
ln -sf ../%{name}/aarch64/vars-template-pflash.raw %{buildroot}/usr/share/AAVMF/AAVMF_VARS.fd
|
Ship the JSON firmware "descriptor files"
From version 4.1 (due in August 2019) onwards, QEMU ships the so-called
firmware "descriptor files". These are small JSON files that describe
details about UEFI firmware binaries — such as the fimware binary path,
its architecture, supported machine type, NVRAM template and so forth.
You can see examples of these files from the QEMU upstream Git:
https://git.qemu.org/?p=qemu.git;a=tree;f=pc-bios/descriptors
$> tree descriptors/
descriptors/
├── 50-edk2-i386-secure.json
├── 50-edk2-x86_64-secure.json
├── 60-edk2-aarch64.json
├── 60-edk2-arm.json
├── 60-edk2-i386.json
└── 60-edk2-x86_64.json
QEMU 4.1 itself will ship the above files. However, Fedora needs to
ship these file as part of its EDK2 package.
Why?
----
(1) Quoting (with minor formatting edits) Laszlo Ersek:
Distributions providing their own EDK2 packages would not include
the descriptors from upstream QEMU, even if they otherwise package
QEMU. That's beause the descriptor files in QEMU match the
firmware bundled with QEMU -- but the firmware images in the
distros' own EDK2 packages are different. So, if a distro
provides an EDK2 package, then the same EDK2 package should offer
matching descriptors. QEMU offers descriptors (soon) because QEMU
technically distributes edk2 firmware binaries (soon). [Where
"soon" == QEMU 4.1]
(2) And as Dan Berrangé reminded on IRC:
In Fedora, we need to ship them [the "descriptor files"] as part
of the EDK2 package, because Fedora throws away all the firmware
files that QEMU bundles, because we're [Fedora] required to
rebuild everything from pristine source.
- - -
In this patch:
(*) Use the firmware descriptor files provided by Laszlo (thanks!) in
this comment here:
https://bugzilla.redhat.com/show_bug.cgi?id=1728652#c2 ("RFE: Ship
the JSON firmware "descriptor files" as part of EDK2").
On the double-digit priority prefixes, refer to the rationale here:
https://src.fedoraproject.org/rpms/edk2/pull-request/3#comment-27523
(*) Install the JSON files for the relevant architectures in
`/usr/share/qemu/firmware`, as required by specification[+]. And
make each EDK2 own this directory; multiple RPMs owning the same
directory is no problem.
[+] https://git.qemu.org/?p=qemu.git;a=blob;f=docs/interop/firmware.json
Resolves: rhbz#1728652
Signed-off-by: Kashyap Chamarthy <kchamart@redhat.com>
2019-07-12 09:20:38 +00:00
|
|
|
|
|
|
|
|
# Install the AArch64 firmware descriptor file (60-edk2-aarch64.json)
|
|
|
|
|
install -pm 644 %{SOURCE20} %{buildroot}/%{_datadir}/qemu/firmware
|
2017-11-13 17:44:20 +00:00
|
|
|
%endif
|
|
|
|
|
%if 0%{?build_aavmf_arm:1}
|
2016-07-21 21:47:43 +00:00
|
|
|
cp -a arm %{buildroot}/usr/share/%{name}
|
2017-11-13 17:44:20 +00:00
|
|
|
ln -sf ../%{name}/arm/QEMU_EFI-pflash.raw %{buildroot}/usr/share/AAVMF/AAVMF32_CODE.fd
|
Ship the JSON firmware "descriptor files"
From version 4.1 (due in August 2019) onwards, QEMU ships the so-called
firmware "descriptor files". These are small JSON files that describe
details about UEFI firmware binaries — such as the fimware binary path,
its architecture, supported machine type, NVRAM template and so forth.
You can see examples of these files from the QEMU upstream Git:
https://git.qemu.org/?p=qemu.git;a=tree;f=pc-bios/descriptors
$> tree descriptors/
descriptors/
├── 50-edk2-i386-secure.json
├── 50-edk2-x86_64-secure.json
├── 60-edk2-aarch64.json
├── 60-edk2-arm.json
├── 60-edk2-i386.json
└── 60-edk2-x86_64.json
QEMU 4.1 itself will ship the above files. However, Fedora needs to
ship these file as part of its EDK2 package.
Why?
----
(1) Quoting (with minor formatting edits) Laszlo Ersek:
Distributions providing their own EDK2 packages would not include
the descriptors from upstream QEMU, even if they otherwise package
QEMU. That's beause the descriptor files in QEMU match the
firmware bundled with QEMU -- but the firmware images in the
distros' own EDK2 packages are different. So, if a distro
provides an EDK2 package, then the same EDK2 package should offer
matching descriptors. QEMU offers descriptors (soon) because QEMU
technically distributes edk2 firmware binaries (soon). [Where
"soon" == QEMU 4.1]
(2) And as Dan Berrangé reminded on IRC:
In Fedora, we need to ship them [the "descriptor files"] as part
of the EDK2 package, because Fedora throws away all the firmware
files that QEMU bundles, because we're [Fedora] required to
rebuild everything from pristine source.
- - -
In this patch:
(*) Use the firmware descriptor files provided by Laszlo (thanks!) in
this comment here:
https://bugzilla.redhat.com/show_bug.cgi?id=1728652#c2 ("RFE: Ship
the JSON firmware "descriptor files" as part of EDK2").
On the double-digit priority prefixes, refer to the rationale here:
https://src.fedoraproject.org/rpms/edk2/pull-request/3#comment-27523
(*) Install the JSON files for the relevant architectures in
`/usr/share/qemu/firmware`, as required by specification[+]. And
make each EDK2 own this directory; multiple RPMs owning the same
directory is no problem.
[+] https://git.qemu.org/?p=qemu.git;a=blob;f=docs/interop/firmware.json
Resolves: rhbz#1728652
Signed-off-by: Kashyap Chamarthy <kchamart@redhat.com>
2019-07-12 09:20:38 +00:00
|
|
|
# Install the ARM firmware descriptor file (60-edk2-arm.json)
|
|
|
|
|
install -pm 644 %{SOURCE21} %{buildroot}/%{_datadir}/qemu/firmware
|
2017-11-13 17:44:20 +00:00
|
|
|
%endif
|
2016-05-21 14:39:41 +00:00
|
|
|
|
2018-04-30 11:57:51 +00:00
|
|
|
install qemu-ovmf-secureboot-%{qosb_version}/ovmf-vars-generator %{buildroot}%{_bindir}
|
|
|
|
|
|
2016-04-18 12:16:51 +00:00
|
|
|
|
2013-05-02 12:46:06 +00:00
|
|
|
%files tools
|
2017-11-14 15:05:26 +00:00
|
|
|
%license License.txt
|
2018-07-18 14:33:51 +00:00
|
|
|
%license LICENSE.openssl
|
2017-11-14 15:05:26 +00:00
|
|
|
%{_bindir}/Brotli
|
2018-05-29 21:06:35 +00:00
|
|
|
%{_bindir}/DevicePath
|
2013-05-02 12:46:06 +00:00
|
|
|
%{_bindir}/EfiRom
|
|
|
|
|
%{_bindir}/GenCrc32
|
|
|
|
|
%{_bindir}/GenFfs
|
|
|
|
|
%{_bindir}/GenFv
|
|
|
|
|
%{_bindir}/GenFw
|
|
|
|
|
%{_bindir}/GenSec
|
|
|
|
|
%{_bindir}/LzmaCompress
|
2014-06-23 15:25:24 +00:00
|
|
|
%{_bindir}/LzmaF86Compress
|
2013-05-02 12:46:06 +00:00
|
|
|
%{_bindir}/Split
|
2014-06-23 15:25:24 +00:00
|
|
|
%{_bindir}/TianoCompress
|
2013-05-02 12:46:06 +00:00
|
|
|
%{_bindir}/VfrCompile
|
|
|
|
|
%{_bindir}/VolInfo
|
2016-04-18 12:16:51 +00:00
|
|
|
%dir %{_datadir}/%{name}
|
2014-06-24 07:50:13 +00:00
|
|
|
%{_datadir}/%{name}/BuildEnv
|
2016-04-18 12:16:51 +00:00
|
|
|
%{_datadir}/%{name}/Conf
|
|
|
|
|
%{_datadir}/%{name}/Scripts
|
2013-05-02 12:46:06 +00:00
|
|
|
|
|
|
|
|
%files tools-python
|
2014-06-23 15:25:24 +00:00
|
|
|
%{_bindir}/build
|
2013-05-02 12:46:06 +00:00
|
|
|
%{_bindir}/BPDG
|
2014-06-23 15:25:24 +00:00
|
|
|
%{_bindir}/Ecc
|
2013-05-02 12:46:06 +00:00
|
|
|
%{_bindir}/GenDepex
|
|
|
|
|
%{_bindir}/GenFds
|
|
|
|
|
%{_bindir}/GenPatchPcdTable
|
|
|
|
|
%{_bindir}/PatchPcdValue
|
|
|
|
|
%{_bindir}/TargetTool
|
|
|
|
|
%{_bindir}/Trim
|
|
|
|
|
%{_bindir}/UPT
|
2016-04-18 12:16:51 +00:00
|
|
|
%dir %{_datadir}/%{name}
|
|
|
|
|
%{_datadir}/%{name}/Python
|
2013-05-02 12:46:06 +00:00
|
|
|
|
|
|
|
|
%files tools-doc
|
2016-04-18 12:16:51 +00:00
|
|
|
%doc BaseTools/UserManuals/*.rtf
|
|
|
|
|
|
2018-04-30 11:57:51 +00:00
|
|
|
%files qosb
|
|
|
|
|
%license LICENSE.qosb
|
|
|
|
|
%doc README.qosb
|
|
|
|
|
%{_bindir}/ovmf-vars-generator
|
|
|
|
|
|
2017-11-13 17:44:20 +00:00
|
|
|
%if 0%{?build_ovmf_x64:1}
|
2016-04-18 12:16:51 +00:00
|
|
|
%files ovmf
|
|
|
|
|
%license OvmfPkg/License.txt
|
|
|
|
|
%license LICENSE.openssl
|
|
|
|
|
%doc OvmfPkg/README
|
2017-11-14 15:05:26 +00:00
|
|
|
%doc ovmf-whitepaper-c770f8c.txt
|
2016-04-18 12:16:51 +00:00
|
|
|
%dir /usr/share/%{name}
|
|
|
|
|
%dir /usr/share/%{name}/ovmf
|
Ship the JSON firmware "descriptor files"
From version 4.1 (due in August 2019) onwards, QEMU ships the so-called
firmware "descriptor files". These are small JSON files that describe
details about UEFI firmware binaries — such as the fimware binary path,
its architecture, supported machine type, NVRAM template and so forth.
You can see examples of these files from the QEMU upstream Git:
https://git.qemu.org/?p=qemu.git;a=tree;f=pc-bios/descriptors
$> tree descriptors/
descriptors/
├── 50-edk2-i386-secure.json
├── 50-edk2-x86_64-secure.json
├── 60-edk2-aarch64.json
├── 60-edk2-arm.json
├── 60-edk2-i386.json
└── 60-edk2-x86_64.json
QEMU 4.1 itself will ship the above files. However, Fedora needs to
ship these file as part of its EDK2 package.
Why?
----
(1) Quoting (with minor formatting edits) Laszlo Ersek:
Distributions providing their own EDK2 packages would not include
the descriptors from upstream QEMU, even if they otherwise package
QEMU. That's beause the descriptor files in QEMU match the
firmware bundled with QEMU -- but the firmware images in the
distros' own EDK2 packages are different. So, if a distro
provides an EDK2 package, then the same EDK2 package should offer
matching descriptors. QEMU offers descriptors (soon) because QEMU
technically distributes edk2 firmware binaries (soon). [Where
"soon" == QEMU 4.1]
(2) And as Dan Berrangé reminded on IRC:
In Fedora, we need to ship them [the "descriptor files"] as part
of the EDK2 package, because Fedora throws away all the firmware
files that QEMU bundles, because we're [Fedora] required to
rebuild everything from pristine source.
- - -
In this patch:
(*) Use the firmware descriptor files provided by Laszlo (thanks!) in
this comment here:
https://bugzilla.redhat.com/show_bug.cgi?id=1728652#c2 ("RFE: Ship
the JSON firmware "descriptor files" as part of EDK2").
On the double-digit priority prefixes, refer to the rationale here:
https://src.fedoraproject.org/rpms/edk2/pull-request/3#comment-27523
(*) Install the JSON files for the relevant architectures in
`/usr/share/qemu/firmware`, as required by specification[+]. And
make each EDK2 own this directory; multiple RPMs owning the same
directory is no problem.
[+] https://git.qemu.org/?p=qemu.git;a=blob;f=docs/interop/firmware.json
Resolves: rhbz#1728652
Signed-off-by: Kashyap Chamarthy <kchamart@redhat.com>
2019-07-12 09:20:38 +00:00
|
|
|
%dir /usr/share/qemu/firmware
|
2016-04-18 12:16:51 +00:00
|
|
|
/usr/share/%{name}/ovmf/OVMF*.fd
|
|
|
|
|
/usr/share/%{name}/ovmf/*.efi
|
|
|
|
|
/usr/share/%{name}/ovmf/*.iso
|
Ship the JSON firmware "descriptor files"
From version 4.1 (due in August 2019) onwards, QEMU ships the so-called
firmware "descriptor files". These are small JSON files that describe
details about UEFI firmware binaries — such as the fimware binary path,
its architecture, supported machine type, NVRAM template and so forth.
You can see examples of these files from the QEMU upstream Git:
https://git.qemu.org/?p=qemu.git;a=tree;f=pc-bios/descriptors
$> tree descriptors/
descriptors/
├── 50-edk2-i386-secure.json
├── 50-edk2-x86_64-secure.json
├── 60-edk2-aarch64.json
├── 60-edk2-arm.json
├── 60-edk2-i386.json
└── 60-edk2-x86_64.json
QEMU 4.1 itself will ship the above files. However, Fedora needs to
ship these file as part of its EDK2 package.
Why?
----
(1) Quoting (with minor formatting edits) Laszlo Ersek:
Distributions providing their own EDK2 packages would not include
the descriptors from upstream QEMU, even if they otherwise package
QEMU. That's beause the descriptor files in QEMU match the
firmware bundled with QEMU -- but the firmware images in the
distros' own EDK2 packages are different. So, if a distro
provides an EDK2 package, then the same EDK2 package should offer
matching descriptors. QEMU offers descriptors (soon) because QEMU
technically distributes edk2 firmware binaries (soon). [Where
"soon" == QEMU 4.1]
(2) And as Dan Berrangé reminded on IRC:
In Fedora, we need to ship them [the "descriptor files"] as part
of the EDK2 package, because Fedora throws away all the firmware
files that QEMU bundles, because we're [Fedora] required to
rebuild everything from pristine source.
- - -
In this patch:
(*) Use the firmware descriptor files provided by Laszlo (thanks!) in
this comment here:
https://bugzilla.redhat.com/show_bug.cgi?id=1728652#c2 ("RFE: Ship
the JSON firmware "descriptor files" as part of EDK2").
On the double-digit priority prefixes, refer to the rationale here:
https://src.fedoraproject.org/rpms/edk2/pull-request/3#comment-27523
(*) Install the JSON files for the relevant architectures in
`/usr/share/qemu/firmware`, as required by specification[+]. And
make each EDK2 own this directory; multiple RPMs owning the same
directory is no problem.
[+] https://git.qemu.org/?p=qemu.git;a=blob;f=docs/interop/firmware.json
Resolves: rhbz#1728652
Signed-off-by: Kashyap Chamarthy <kchamart@redhat.com>
2019-07-12 09:20:38 +00:00
|
|
|
/usr/share/qemu/firmware/*.json
|
2017-11-13 17:44:20 +00:00
|
|
|
/usr/share/OVMF
|
|
|
|
|
%endif
|
2016-04-18 12:16:51 +00:00
|
|
|
|
2017-11-13 17:44:20 +00:00
|
|
|
%if 0%{?build_ovmf_ia32:1}
|
2017-03-15 21:56:49 +00:00
|
|
|
%files ovmf-ia32
|
|
|
|
|
%license OvmfPkg/License.txt
|
|
|
|
|
%license LICENSE.openssl
|
|
|
|
|
%doc OvmfPkg/README
|
2017-11-14 15:05:26 +00:00
|
|
|
%doc ovmf-whitepaper-c770f8c.txt
|
2017-03-15 21:56:49 +00:00
|
|
|
%dir /usr/share/%{name}
|
|
|
|
|
%dir /usr/share/%{name}/ovmf-ia32
|
Ship the JSON firmware "descriptor files"
From version 4.1 (due in August 2019) onwards, QEMU ships the so-called
firmware "descriptor files". These are small JSON files that describe
details about UEFI firmware binaries — such as the fimware binary path,
its architecture, supported machine type, NVRAM template and so forth.
You can see examples of these files from the QEMU upstream Git:
https://git.qemu.org/?p=qemu.git;a=tree;f=pc-bios/descriptors
$> tree descriptors/
descriptors/
├── 50-edk2-i386-secure.json
├── 50-edk2-x86_64-secure.json
├── 60-edk2-aarch64.json
├── 60-edk2-arm.json
├── 60-edk2-i386.json
└── 60-edk2-x86_64.json
QEMU 4.1 itself will ship the above files. However, Fedora needs to
ship these file as part of its EDK2 package.
Why?
----
(1) Quoting (with minor formatting edits) Laszlo Ersek:
Distributions providing their own EDK2 packages would not include
the descriptors from upstream QEMU, even if they otherwise package
QEMU. That's beause the descriptor files in QEMU match the
firmware bundled with QEMU -- but the firmware images in the
distros' own EDK2 packages are different. So, if a distro
provides an EDK2 package, then the same EDK2 package should offer
matching descriptors. QEMU offers descriptors (soon) because QEMU
technically distributes edk2 firmware binaries (soon). [Where
"soon" == QEMU 4.1]
(2) And as Dan Berrangé reminded on IRC:
In Fedora, we need to ship them [the "descriptor files"] as part
of the EDK2 package, because Fedora throws away all the firmware
files that QEMU bundles, because we're [Fedora] required to
rebuild everything from pristine source.
- - -
In this patch:
(*) Use the firmware descriptor files provided by Laszlo (thanks!) in
this comment here:
https://bugzilla.redhat.com/show_bug.cgi?id=1728652#c2 ("RFE: Ship
the JSON firmware "descriptor files" as part of EDK2").
On the double-digit priority prefixes, refer to the rationale here:
https://src.fedoraproject.org/rpms/edk2/pull-request/3#comment-27523
(*) Install the JSON files for the relevant architectures in
`/usr/share/qemu/firmware`, as required by specification[+]. And
make each EDK2 own this directory; multiple RPMs owning the same
directory is no problem.
[+] https://git.qemu.org/?p=qemu.git;a=blob;f=docs/interop/firmware.json
Resolves: rhbz#1728652
Signed-off-by: Kashyap Chamarthy <kchamart@redhat.com>
2019-07-12 09:20:38 +00:00
|
|
|
%dir /usr/share/qemu/firmware
|
2017-03-15 21:56:49 +00:00
|
|
|
/usr/share/%{name}/ovmf-ia32/OVMF*.fd
|
|
|
|
|
/usr/share/%{name}/ovmf-ia32/*.efi
|
|
|
|
|
/usr/share/%{name}/ovmf-ia32/*.iso
|
Ship the JSON firmware "descriptor files"
From version 4.1 (due in August 2019) onwards, QEMU ships the so-called
firmware "descriptor files". These are small JSON files that describe
details about UEFI firmware binaries — such as the fimware binary path,
its architecture, supported machine type, NVRAM template and so forth.
You can see examples of these files from the QEMU upstream Git:
https://git.qemu.org/?p=qemu.git;a=tree;f=pc-bios/descriptors
$> tree descriptors/
descriptors/
├── 50-edk2-i386-secure.json
├── 50-edk2-x86_64-secure.json
├── 60-edk2-aarch64.json
├── 60-edk2-arm.json
├── 60-edk2-i386.json
└── 60-edk2-x86_64.json
QEMU 4.1 itself will ship the above files. However, Fedora needs to
ship these file as part of its EDK2 package.
Why?
----
(1) Quoting (with minor formatting edits) Laszlo Ersek:
Distributions providing their own EDK2 packages would not include
the descriptors from upstream QEMU, even if they otherwise package
QEMU. That's beause the descriptor files in QEMU match the
firmware bundled with QEMU -- but the firmware images in the
distros' own EDK2 packages are different. So, if a distro
provides an EDK2 package, then the same EDK2 package should offer
matching descriptors. QEMU offers descriptors (soon) because QEMU
technically distributes edk2 firmware binaries (soon). [Where
"soon" == QEMU 4.1]
(2) And as Dan Berrangé reminded on IRC:
In Fedora, we need to ship them [the "descriptor files"] as part
of the EDK2 package, because Fedora throws away all the firmware
files that QEMU bundles, because we're [Fedora] required to
rebuild everything from pristine source.
- - -
In this patch:
(*) Use the firmware descriptor files provided by Laszlo (thanks!) in
this comment here:
https://bugzilla.redhat.com/show_bug.cgi?id=1728652#c2 ("RFE: Ship
the JSON firmware "descriptor files" as part of EDK2").
On the double-digit priority prefixes, refer to the rationale here:
https://src.fedoraproject.org/rpms/edk2/pull-request/3#comment-27523
(*) Install the JSON files for the relevant architectures in
`/usr/share/qemu/firmware`, as required by specification[+]. And
make each EDK2 own this directory; multiple RPMs owning the same
directory is no problem.
[+] https://git.qemu.org/?p=qemu.git;a=blob;f=docs/interop/firmware.json
Resolves: rhbz#1728652
Signed-off-by: Kashyap Chamarthy <kchamart@redhat.com>
2019-07-12 09:20:38 +00:00
|
|
|
/usr/share/qemu/firmware/*.json
|
2017-11-13 17:44:20 +00:00
|
|
|
%endif
|
2017-03-15 21:56:49 +00:00
|
|
|
|
2017-11-13 17:44:20 +00:00
|
|
|
%if 0%{?build_aavmf_aarch64:1}
|
2016-04-18 12:16:51 +00:00
|
|
|
%files aarch64
|
2017-11-14 15:05:26 +00:00
|
|
|
%license OvmfPkg/License.txt
|
|
|
|
|
%license LICENSE.openssl
|
2016-04-18 12:16:51 +00:00
|
|
|
%dir /usr/share/%{name}
|
|
|
|
|
%dir /usr/share/%{name}/aarch64
|
Ship the JSON firmware "descriptor files"
From version 4.1 (due in August 2019) onwards, QEMU ships the so-called
firmware "descriptor files". These are small JSON files that describe
details about UEFI firmware binaries — such as the fimware binary path,
its architecture, supported machine type, NVRAM template and so forth.
You can see examples of these files from the QEMU upstream Git:
https://git.qemu.org/?p=qemu.git;a=tree;f=pc-bios/descriptors
$> tree descriptors/
descriptors/
├── 50-edk2-i386-secure.json
├── 50-edk2-x86_64-secure.json
├── 60-edk2-aarch64.json
├── 60-edk2-arm.json
├── 60-edk2-i386.json
└── 60-edk2-x86_64.json
QEMU 4.1 itself will ship the above files. However, Fedora needs to
ship these file as part of its EDK2 package.
Why?
----
(1) Quoting (with minor formatting edits) Laszlo Ersek:
Distributions providing their own EDK2 packages would not include
the descriptors from upstream QEMU, even if they otherwise package
QEMU. That's beause the descriptor files in QEMU match the
firmware bundled with QEMU -- but the firmware images in the
distros' own EDK2 packages are different. So, if a distro
provides an EDK2 package, then the same EDK2 package should offer
matching descriptors. QEMU offers descriptors (soon) because QEMU
technically distributes edk2 firmware binaries (soon). [Where
"soon" == QEMU 4.1]
(2) And as Dan Berrangé reminded on IRC:
In Fedora, we need to ship them [the "descriptor files"] as part
of the EDK2 package, because Fedora throws away all the firmware
files that QEMU bundles, because we're [Fedora] required to
rebuild everything from pristine source.
- - -
In this patch:
(*) Use the firmware descriptor files provided by Laszlo (thanks!) in
this comment here:
https://bugzilla.redhat.com/show_bug.cgi?id=1728652#c2 ("RFE: Ship
the JSON firmware "descriptor files" as part of EDK2").
On the double-digit priority prefixes, refer to the rationale here:
https://src.fedoraproject.org/rpms/edk2/pull-request/3#comment-27523
(*) Install the JSON files for the relevant architectures in
`/usr/share/qemu/firmware`, as required by specification[+]. And
make each EDK2 own this directory; multiple RPMs owning the same
directory is no problem.
[+] https://git.qemu.org/?p=qemu.git;a=blob;f=docs/interop/firmware.json
Resolves: rhbz#1728652
Signed-off-by: Kashyap Chamarthy <kchamart@redhat.com>
2019-07-12 09:20:38 +00:00
|
|
|
%dir /usr/share/qemu/firmware
|
2016-04-18 12:16:51 +00:00
|
|
|
/usr/share/%{name}/aarch64/QEMU*.fd
|
|
|
|
|
/usr/share/%{name}/aarch64/*.raw
|
Ship the JSON firmware "descriptor files"
From version 4.1 (due in August 2019) onwards, QEMU ships the so-called
firmware "descriptor files". These are small JSON files that describe
details about UEFI firmware binaries — such as the fimware binary path,
its architecture, supported machine type, NVRAM template and so forth.
You can see examples of these files from the QEMU upstream Git:
https://git.qemu.org/?p=qemu.git;a=tree;f=pc-bios/descriptors
$> tree descriptors/
descriptors/
├── 50-edk2-i386-secure.json
├── 50-edk2-x86_64-secure.json
├── 60-edk2-aarch64.json
├── 60-edk2-arm.json
├── 60-edk2-i386.json
└── 60-edk2-x86_64.json
QEMU 4.1 itself will ship the above files. However, Fedora needs to
ship these file as part of its EDK2 package.
Why?
----
(1) Quoting (with minor formatting edits) Laszlo Ersek:
Distributions providing their own EDK2 packages would not include
the descriptors from upstream QEMU, even if they otherwise package
QEMU. That's beause the descriptor files in QEMU match the
firmware bundled with QEMU -- but the firmware images in the
distros' own EDK2 packages are different. So, if a distro
provides an EDK2 package, then the same EDK2 package should offer
matching descriptors. QEMU offers descriptors (soon) because QEMU
technically distributes edk2 firmware binaries (soon). [Where
"soon" == QEMU 4.1]
(2) And as Dan Berrangé reminded on IRC:
In Fedora, we need to ship them [the "descriptor files"] as part
of the EDK2 package, because Fedora throws away all the firmware
files that QEMU bundles, because we're [Fedora] required to
rebuild everything from pristine source.
- - -
In this patch:
(*) Use the firmware descriptor files provided by Laszlo (thanks!) in
this comment here:
https://bugzilla.redhat.com/show_bug.cgi?id=1728652#c2 ("RFE: Ship
the JSON firmware "descriptor files" as part of EDK2").
On the double-digit priority prefixes, refer to the rationale here:
https://src.fedoraproject.org/rpms/edk2/pull-request/3#comment-27523
(*) Install the JSON files for the relevant architectures in
`/usr/share/qemu/firmware`, as required by specification[+]. And
make each EDK2 own this directory; multiple RPMs owning the same
directory is no problem.
[+] https://git.qemu.org/?p=qemu.git;a=blob;f=docs/interop/firmware.json
Resolves: rhbz#1728652
Signed-off-by: Kashyap Chamarthy <kchamart@redhat.com>
2019-07-12 09:20:38 +00:00
|
|
|
/usr/share/qemu/firmware/*.json
|
2017-11-13 17:44:20 +00:00
|
|
|
/usr/share/AAVMF/AAVMF_*
|
|
|
|
|
%endif
|
2016-05-21 14:39:41 +00:00
|
|
|
|
2017-11-13 17:44:20 +00:00
|
|
|
%if 0%{?build_aavmf_arm:1}
|
2016-07-21 21:47:43 +00:00
|
|
|
%files arm
|
2017-11-14 15:05:26 +00:00
|
|
|
%license OvmfPkg/License.txt
|
|
|
|
|
%license LICENSE.openssl
|
2016-07-21 21:47:43 +00:00
|
|
|
%dir /usr/share/%{name}
|
|
|
|
|
%dir /usr/share/%{name}/arm
|
Ship the JSON firmware "descriptor files"
From version 4.1 (due in August 2019) onwards, QEMU ships the so-called
firmware "descriptor files". These are small JSON files that describe
details about UEFI firmware binaries — such as the fimware binary path,
its architecture, supported machine type, NVRAM template and so forth.
You can see examples of these files from the QEMU upstream Git:
https://git.qemu.org/?p=qemu.git;a=tree;f=pc-bios/descriptors
$> tree descriptors/
descriptors/
├── 50-edk2-i386-secure.json
├── 50-edk2-x86_64-secure.json
├── 60-edk2-aarch64.json
├── 60-edk2-arm.json
├── 60-edk2-i386.json
└── 60-edk2-x86_64.json
QEMU 4.1 itself will ship the above files. However, Fedora needs to
ship these file as part of its EDK2 package.
Why?
----
(1) Quoting (with minor formatting edits) Laszlo Ersek:
Distributions providing their own EDK2 packages would not include
the descriptors from upstream QEMU, even if they otherwise package
QEMU. That's beause the descriptor files in QEMU match the
firmware bundled with QEMU -- but the firmware images in the
distros' own EDK2 packages are different. So, if a distro
provides an EDK2 package, then the same EDK2 package should offer
matching descriptors. QEMU offers descriptors (soon) because QEMU
technically distributes edk2 firmware binaries (soon). [Where
"soon" == QEMU 4.1]
(2) And as Dan Berrangé reminded on IRC:
In Fedora, we need to ship them [the "descriptor files"] as part
of the EDK2 package, because Fedora throws away all the firmware
files that QEMU bundles, because we're [Fedora] required to
rebuild everything from pristine source.
- - -
In this patch:
(*) Use the firmware descriptor files provided by Laszlo (thanks!) in
this comment here:
https://bugzilla.redhat.com/show_bug.cgi?id=1728652#c2 ("RFE: Ship
the JSON firmware "descriptor files" as part of EDK2").
On the double-digit priority prefixes, refer to the rationale here:
https://src.fedoraproject.org/rpms/edk2/pull-request/3#comment-27523
(*) Install the JSON files for the relevant architectures in
`/usr/share/qemu/firmware`, as required by specification[+]. And
make each EDK2 own this directory; multiple RPMs owning the same
directory is no problem.
[+] https://git.qemu.org/?p=qemu.git;a=blob;f=docs/interop/firmware.json
Resolves: rhbz#1728652
Signed-off-by: Kashyap Chamarthy <kchamart@redhat.com>
2019-07-12 09:20:38 +00:00
|
|
|
%dir /usr/share/qemu/firmware
|
2016-07-21 21:47:43 +00:00
|
|
|
/usr/share/%{name}/arm/QEMU*.fd
|
|
|
|
|
/usr/share/%{name}/arm/*.raw
|
Ship the JSON firmware "descriptor files"
From version 4.1 (due in August 2019) onwards, QEMU ships the so-called
firmware "descriptor files". These are small JSON files that describe
details about UEFI firmware binaries — such as the fimware binary path,
its architecture, supported machine type, NVRAM template and so forth.
You can see examples of these files from the QEMU upstream Git:
https://git.qemu.org/?p=qemu.git;a=tree;f=pc-bios/descriptors
$> tree descriptors/
descriptors/
├── 50-edk2-i386-secure.json
├── 50-edk2-x86_64-secure.json
├── 60-edk2-aarch64.json
├── 60-edk2-arm.json
├── 60-edk2-i386.json
└── 60-edk2-x86_64.json
QEMU 4.1 itself will ship the above files. However, Fedora needs to
ship these file as part of its EDK2 package.
Why?
----
(1) Quoting (with minor formatting edits) Laszlo Ersek:
Distributions providing their own EDK2 packages would not include
the descriptors from upstream QEMU, even if they otherwise package
QEMU. That's beause the descriptor files in QEMU match the
firmware bundled with QEMU -- but the firmware images in the
distros' own EDK2 packages are different. So, if a distro
provides an EDK2 package, then the same EDK2 package should offer
matching descriptors. QEMU offers descriptors (soon) because QEMU
technically distributes edk2 firmware binaries (soon). [Where
"soon" == QEMU 4.1]
(2) And as Dan Berrangé reminded on IRC:
In Fedora, we need to ship them [the "descriptor files"] as part
of the EDK2 package, because Fedora throws away all the firmware
files that QEMU bundles, because we're [Fedora] required to
rebuild everything from pristine source.
- - -
In this patch:
(*) Use the firmware descriptor files provided by Laszlo (thanks!) in
this comment here:
https://bugzilla.redhat.com/show_bug.cgi?id=1728652#c2 ("RFE: Ship
the JSON firmware "descriptor files" as part of EDK2").
On the double-digit priority prefixes, refer to the rationale here:
https://src.fedoraproject.org/rpms/edk2/pull-request/3#comment-27523
(*) Install the JSON files for the relevant architectures in
`/usr/share/qemu/firmware`, as required by specification[+]. And
make each EDK2 own this directory; multiple RPMs owning the same
directory is no problem.
[+] https://git.qemu.org/?p=qemu.git;a=blob;f=docs/interop/firmware.json
Resolves: rhbz#1728652
Signed-off-by: Kashyap Chamarthy <kchamart@redhat.com>
2019-07-12 09:20:38 +00:00
|
|
|
/usr/share/qemu/firmware/*.json
|
2017-11-13 17:44:20 +00:00
|
|
|
/usr/share/AAVMF/AAVMF32_*
|
|
|
|
|
%endif
|
2016-07-21 21:47:43 +00:00
|
|
|
|
2013-05-02 12:46:06 +00:00
|
|
|
|
|
|
|
|
%changelog
|
2019-07-11 23:42:10 +00:00
|
|
|
* Thu Jul 11 2019 Cole Robinson <crobinso@redhat.com> - 20190501stable-1
|
|
|
|
|
- Update to stable-201905
|
|
|
|
|
- Update to openssl-1.1.1b
|
2019-07-12 17:06:37 +00:00
|
|
|
- Ship VARS file for ovmf-ia32 (bug 1688596)
|
Ship the JSON firmware "descriptor files"
From version 4.1 (due in August 2019) onwards, QEMU ships the so-called
firmware "descriptor files". These are small JSON files that describe
details about UEFI firmware binaries — such as the fimware binary path,
its architecture, supported machine type, NVRAM template and so forth.
You can see examples of these files from the QEMU upstream Git:
https://git.qemu.org/?p=qemu.git;a=tree;f=pc-bios/descriptors
$> tree descriptors/
descriptors/
├── 50-edk2-i386-secure.json
├── 50-edk2-x86_64-secure.json
├── 60-edk2-aarch64.json
├── 60-edk2-arm.json
├── 60-edk2-i386.json
└── 60-edk2-x86_64.json
QEMU 4.1 itself will ship the above files. However, Fedora needs to
ship these file as part of its EDK2 package.
Why?
----
(1) Quoting (with minor formatting edits) Laszlo Ersek:
Distributions providing their own EDK2 packages would not include
the descriptors from upstream QEMU, even if they otherwise package
QEMU. That's beause the descriptor files in QEMU match the
firmware bundled with QEMU -- but the firmware images in the
distros' own EDK2 packages are different. So, if a distro
provides an EDK2 package, then the same EDK2 package should offer
matching descriptors. QEMU offers descriptors (soon) because QEMU
technically distributes edk2 firmware binaries (soon). [Where
"soon" == QEMU 4.1]
(2) And as Dan Berrangé reminded on IRC:
In Fedora, we need to ship them [the "descriptor files"] as part
of the EDK2 package, because Fedora throws away all the firmware
files that QEMU bundles, because we're [Fedora] required to
rebuild everything from pristine source.
- - -
In this patch:
(*) Use the firmware descriptor files provided by Laszlo (thanks!) in
this comment here:
https://bugzilla.redhat.com/show_bug.cgi?id=1728652#c2 ("RFE: Ship
the JSON firmware "descriptor files" as part of EDK2").
On the double-digit priority prefixes, refer to the rationale here:
https://src.fedoraproject.org/rpms/edk2/pull-request/3#comment-27523
(*) Install the JSON files for the relevant architectures in
`/usr/share/qemu/firmware`, as required by specification[+]. And
make each EDK2 own this directory; multiple RPMs owning the same
directory is no problem.
[+] https://git.qemu.org/?p=qemu.git;a=blob;f=docs/interop/firmware.json
Resolves: rhbz#1728652
Signed-off-by: Kashyap Chamarthy <kchamart@redhat.com>
2019-07-12 09:20:38 +00:00
|
|
|
- Ship Fedora-variant JSON "firmware descriptor files"
|
|
|
|
|
- Resolves rhbz#1728652
|
2019-07-11 23:42:10 +00:00
|
|
|
|
2019-03-18 15:03:41 +00:00
|
|
|
* Mon Mar 18 2019 Cole Robinson <aintdiscole@gmail.com> - 20190308stable-1
|
|
|
|
|
- Use YYYYMMDD versioning to fix upgrade path
|
|
|
|
|
|
|
|
|
|
* Fri Mar 15 2019 Cole Robinson <aintdiscole@gmail.com> - 201903stable-1
|
2019-03-15 16:27:02 +00:00
|
|
|
- Update to stable-201903
|
|
|
|
|
- Update to openssl-1.1.0j
|
|
|
|
|
- Move to python3 deps
|
|
|
|
|
|
2019-01-31 18:22:54 +00:00
|
|
|
* Thu Jan 31 2019 Fedora Release Engineering <releng@fedoraproject.org> - 20180815gitcb5f4f45ce-6
|
|
|
|
|
- Rebuilt for https://fedoraproject.org/wiki/Fedora_30_Mass_Rebuild
|
|
|
|
|
|
2018-11-14 16:10:37 +00:00
|
|
|
* Wed Nov 14 2018 Patrick Uiterwijk <puiterwijk@redhat.com> - 20180815gitcb5f4f45ce-5
|
|
|
|
|
- Add -qosb dependency on python3
|
|
|
|
|
|
2018-11-09 20:13:58 +00:00
|
|
|
* Fri Nov 9 2018 Paolo Bonzini <pbonzini@redhat.com> - 20180815gitcb5f4f45ce-4
|
|
|
|
|
- Fix network boot via grub (bz 1648476)
|
|
|
|
|
|
2018-09-12 13:50:36 +00:00
|
|
|
* Wed Sep 12 2018 Paolo Bonzini <pbonzini@redhat.com> - 20180815gitcb5f4f45ce-3
|
|
|
|
|
- Explicitly compile the scripts using py_byte_compile
|
|
|
|
|
|
2018-08-31 17:07:49 +00:00
|
|
|
* Fri Aug 31 2018 Cole Robinson <crobinso@redhat.com> - 20180815gitcb5f4f45ce-2
|
|
|
|
|
- Fix passing through RPM build flags (bz 1540244)
|
|
|
|
|
|
2018-08-16 19:50:44 +00:00
|
|
|
* Tue Aug 21 2018 Cole Robinson <crobinso@redhat.com> - 20180815gitcb5f4f45ce-1
|
|
|
|
|
- Update to edk2 git cb5f4f45ce, edk2-stable201808
|
2018-08-22 23:03:42 +00:00
|
|
|
- Update to qemu-ovmf-secureboot-1.1.3
|
|
|
|
|
- Enable TPM2 support
|
2018-08-16 19:50:44 +00:00
|
|
|
|
2018-07-23 08:57:29 +00:00
|
|
|
* Mon Jul 23 2018 Paolo Bonzini <pbonzini@redhat.com> - 20180529gitee3198e672e2-5
|
|
|
|
|
- Fixes for AMD SEV on OVMF_CODE.fd
|
|
|
|
|
- Add Provides for bundled OpenSSL
|
|
|
|
|
|
2018-07-18 14:33:51 +00:00
|
|
|
* Wed Jul 18 2018 Paolo Bonzini <pbonzini@redhat.com> - 20180529gitee3198e672e2-4
|
|
|
|
|
- Enable IPv6
|
|
|
|
|
|
2018-07-12 23:41:16 +00:00
|
|
|
* Thu Jul 12 2018 Fedora Release Engineering <releng@fedoraproject.org> - 20180529gitee3198e672e2-3
|
|
|
|
|
- Rebuilt for https://fedoraproject.org/wiki/Fedora_29_Mass_Rebuild
|
|
|
|
|
|
2018-06-20 08:09:08 +00:00
|
|
|
* Wed Jun 20 2018 Paolo Bonzini <pbonzini@redhat.com> - 20180529gitee3198e672e2-2
|
|
|
|
|
- Backport two bug fixes from RHEL: connect again virtio-rng devices, and
|
|
|
|
|
connect consoles unconditionally in OVMF (ARM firmware already did it)
|
|
|
|
|
|
2018-05-29 21:06:35 +00:00
|
|
|
* Tue May 29 2018 Paolo Bonzini <pbonzini@redhat.com> - 20180529gitee3198e672e2-1
|
2018-06-20 08:09:08 +00:00
|
|
|
- Rebase to ee3198e672e2
|
2018-05-29 21:06:35 +00:00
|
|
|
|
2018-05-01 17:58:41 +00:00
|
|
|
* Tue May 01 2018 Cole Robinson <crobinso@redhat.com> - 20171011git92d07e4-7
|
|
|
|
|
- Bump release for new build
|
|
|
|
|
|
2018-04-30 11:57:51 +00:00
|
|
|
* Fri Mar 30 2018 Patrick Uiterwijk <puiterwijk@redhat.com> - 20171011git92d07e4-6
|
|
|
|
|
- Add qemu-ovmf-secureboot (qosb)
|
|
|
|
|
- Generate pre-enrolled Secure Boot OVMF VARS files
|
|
|
|
|
|
2018-03-08 10:38:21 +00:00
|
|
|
* Wed Mar 07 2018 Paolo Bonzini <pbonzini@redhat.com> - 20171011git92d07e4-5
|
|
|
|
|
- Fix GCC 8 compilation
|
|
|
|
|
- Replace dosfstools and mtools with qemu-img vvfat
|
|
|
|
|
|
2018-02-07 08:12:29 +00:00
|
|
|
* Wed Feb 07 2018 Fedora Release Engineering <releng@fedoraproject.org> - 20171011git92d07e4-4
|
|
|
|
|
- Rebuilt for https://fedoraproject.org/wiki/Fedora_28_Mass_Rebuild
|
|
|
|
|
|
2018-01-19 08:36:03 +00:00
|
|
|
* Fri Jan 19 2018 Paolo Bonzini <pbonzini@redhat.com> - 20170209git296153c5-3
|
|
|
|
|
- Add OpenSSL patches from Fedora
|
|
|
|
|
- Enable TLS_MODE
|
|
|
|
|
|
2017-11-17 07:49:48 +00:00
|
|
|
* Fri Nov 17 2017 Paolo Bonzini <pbonzini@redhat.com> - 20170209git296153c5-2
|
|
|
|
|
- Backport patches 19-21 from RHEL
|
|
|
|
|
- Add patches 22-24 to fix SEV slowness
|
|
|
|
|
- Add fedora conditionals
|
|
|
|
|
|
|
|
|
|
* Tue Nov 14 2017 Paolo Bonzini <pbonzini@redhat.com> - 20171011git92d07e4-1
|
2017-11-14 15:05:26 +00:00
|
|
|
- Import source and patches from RHEL version
|
|
|
|
|
- Update OpenSSL to 1.1.0e
|
|
|
|
|
- Refresh 0099-Tweak-the-tools_def-to-support-cross-compiling.patch
|
|
|
|
|
|
2017-11-13 17:44:20 +00:00
|
|
|
* Mon Nov 13 2017 Paolo Bonzini <pbonzini@redhat.com> - 20170209git296153c5-6
|
|
|
|
|
- Allow non-cross builds
|
|
|
|
|
- Install /usr/share/OVMF and /usr/share/AAVMF
|
|
|
|
|
|
2017-08-02 19:57:57 +00:00
|
|
|
* Wed Aug 02 2017 Fedora Release Engineering <releng@fedoraproject.org> - 20170209git296153c5-5
|
|
|
|
|
- Rebuilt for https://fedoraproject.org/wiki/Fedora_27_Binutils_Mass_Rebuild
|
|
|
|
|
|
2017-07-26 07:12:50 +00:00
|
|
|
* Wed Jul 26 2017 Fedora Release Engineering <releng@fedoraproject.org> - 20170209git296153c5-4
|
|
|
|
|
- Rebuilt for https://fedoraproject.org/wiki/Fedora_27_Mass_Rebuild
|
|
|
|
|
|
2017-03-15 21:56:49 +00:00
|
|
|
* Wed Mar 15 2017 Cole Robinson <crobinso@redhat.com> - 20170209git296153c5-3
|
|
|
|
|
- Ship ovmf-ia32 package (bz 1424722)
|
|
|
|
|
|
2017-02-16 19:15:14 +00:00
|
|
|
* Thu Feb 16 2017 Cole Robinson <crobinso@redhat.com> - 20170209git296153c5-2
|
|
|
|
|
- Update EnrollDefaultKeys patch (bz #1398743)
|
|
|
|
|
|
2017-02-13 11:15:58 +00:00
|
|
|
* Mon Feb 13 2017 Paolo Bonzini <pbonzini@redhat.com> - 20170209git296153c5-1
|
|
|
|
|
- Rebase to git master
|
|
|
|
|
- New patch 0010 fixes failure to build from source.
|
|
|
|
|
|
2017-02-10 09:03:46 +00:00
|
|
|
* Fri Feb 10 2017 Fedora Release Engineering <releng@fedoraproject.org> - 20161105git3b25ca8-2
|
|
|
|
|
- Rebuilt for https://fedoraproject.org/wiki/Fedora_26_Mass_Rebuild
|
|
|
|
|
|
2016-11-06 20:04:24 +00:00
|
|
|
* Sun Nov 06 2016 Cole Robinson <crobinso@redhat.com> - 20161105git3b25ca8-1
|
|
|
|
|
- Rebase to git master
|
|
|
|
|
|
2016-09-09 15:13:22 +00:00
|
|
|
* Fri Sep 9 2016 Tom Callaway <spot@fedoraproject.org> - 20160418gita8c39ba-5
|
|
|
|
|
- replace legally problematic openssl source with "hobbled" tarball
|
|
|
|
|
|
2016-07-21 21:47:43 +00:00
|
|
|
* Thu Jul 21 2016 Gerd Hoffmann <kraxel@redhat.com> - 20160418gita8c39ba-4
|
|
|
|
|
- Also build for armv7.
|
|
|
|
|
|
|
|
|
|
* Tue Jul 19 2016 Gerd Hoffmann <kraxel@redhat.com> 20160418gita8c39ba-3
|
2016-07-19 06:36:46 +00:00
|
|
|
- Update EnrollDefaultKeys patch.
|
|
|
|
|
|
2016-07-08 11:16:59 +00:00
|
|
|
* Fri Jul 8 2016 Paolo Bonzini <pbonzini@redhat.com> - 20160418gita8c39ba-2
|
|
|
|
|
- Distribute edk2-ovmf on aarch64
|
|
|
|
|
|
2016-05-21 14:39:41 +00:00
|
|
|
* Sat May 21 2016 Cole Robinson <crobinso@redhat.com> - 20160418gita8c39ba-1
|
|
|
|
|
- Distribute edk2-aarch64 on x86 (bz #1338027)
|
|
|
|
|
|
2016-04-18 12:16:51 +00:00
|
|
|
* Mon Apr 18 2016 Gerd Hoffmann <kraxel@redhat.com> 20160418gita8c39ba-0
|
|
|
|
|
- Update to latest git.
|
|
|
|
|
- Add firmware builds (FatPkg is free now).
|
|
|
|
|
|
2016-02-15 17:30:33 +00:00
|
|
|
* Mon Feb 15 2016 Cole Robinson <crobinso@redhat.com> 20151127svn18975-3
|
|
|
|
|
- Fix FTBFS gcc warning (bz 1307439)
|
|
|
|
|
|
2016-02-03 19:40:27 +00:00
|
|
|
* Wed Feb 03 2016 Fedora Release Engineering <releng@fedoraproject.org> - 20151127svn18975-2
|
|
|
|
|
- Rebuilt for https://fedoraproject.org/wiki/Fedora_24_Mass_Rebuild
|
|
|
|
|
|
2016-02-15 17:30:33 +00:00
|
|
|
* Fri Nov 27 2015 Paolo Bonzini <pbonzini@redhat.com> - 20151127svn18975-1
|
2015-11-27 13:00:44 +00:00
|
|
|
- Rebase to 20151127svn18975-1
|
|
|
|
|
- Linker script renamed to GccBase.lds
|
|
|
|
|
|
2015-06-17 05:16:07 +00:00
|
|
|
* Wed Jun 17 2015 Fedora Release Engineering <rel-eng@lists.fedoraproject.org> - 20150519svn17469-2
|
|
|
|
|
- Rebuilt for https://fedoraproject.org/wiki/Fedora_23_Mass_Rebuild
|
|
|
|
|
|
2015-11-27 13:00:44 +00:00
|
|
|
* Tue May 19 2015 Paolo Bonzini <pbonzini@redhat.com> - 20150519svn17469-1
|
2015-05-19 10:46:43 +00:00
|
|
|
- Rebase to 20150519svn17469-1
|
|
|
|
|
- edk2-remove-tree-check.patch now upstream
|
|
|
|
|
|
2015-05-02 11:27:18 +00:00
|
|
|
* Sat May 02 2015 Kalev Lember <kalevlember@gmail.com> - 20140724svn2670-6
|
|
|
|
|
- Rebuilt for GCC 5 C++11 ABI change
|
|
|
|
|
|
2014-08-16 10:25:01 +00:00
|
|
|
* Sat Aug 16 2014 Fedora Release Engineering <rel-eng@lists.fedoraproject.org> - 20140724svn2670-5
|
|
|
|
|
- Rebuilt for https://fedoraproject.org/wiki/Fedora_21_22_Mass_Rebuild
|
|
|
|
|
|
2014-07-24 12:27:29 +00:00
|
|
|
* Thu Jul 24 2014 Paolo Bonzini <pbonzini@redhat.com> - 20140724svn2670-1
|
|
|
|
|
- Rebase to 20140724svn2670-1
|
|
|
|
|
|
2014-06-24 08:43:55 +00:00
|
|
|
* Tue Jun 24 2014 Paolo Bonzini <pbonzini@redhat.com> - 20140624svn2649-1
|
|
|
|
|
- Use standalone .tar.xz from buildtools repo
|
|
|
|
|
|
2014-06-24 07:50:13 +00:00
|
|
|
* Tue Jun 24 2014 Paolo Bonzini <pbonzini@redhat.com> - 20140328svn15376-4
|
|
|
|
|
- Install BuildTools/BaseEnv
|
|
|
|
|
|
2014-06-23 15:25:24 +00:00
|
|
|
* Mon Jun 23 2014 Paolo Bonzini <pbonzini@redhat.com> - 20140328svn15376-3
|
|
|
|
|
- Rebase to get GCC48 configuration
|
|
|
|
|
- Package EDK_TOOLS_PATH as /usr/share/edk2
|
|
|
|
|
- Package "build" and LzmaF86Compress too, as well as the new
|
|
|
|
|
tools Ecc and TianoCompress.
|
|
|
|
|
|
2014-06-07 09:55:49 +00:00
|
|
|
* Sat Jun 07 2014 Fedora Release Engineering <rel-eng@lists.fedoraproject.org> - 20131114svn14844-2
|
|
|
|
|
- Rebuilt for https://fedoraproject.org/wiki/Fedora_21_Mass_Rebuild
|
|
|
|
|
|
2013-11-14 14:50:55 +00:00
|
|
|
* Thu Nov 14 2013 Paolo Bonzini <pbonzini@redhat.com> - 20131114svn14844-1
|
|
|
|
|
- Upgrade to r14844.
|
2013-11-14 15:30:12 +00:00
|
|
|
- Remove upstreamed parts of patch 1.
|
2013-11-14 14:50:55 +00:00
|
|
|
|
2013-11-08 13:34:26 +00:00
|
|
|
* Fri Nov 8 2013 Paolo Bonzini <pbonzini@redhat.com> - 20130515svn14365-7
|
|
|
|
|
- Make BaseTools compile on ARM.
|
|
|
|
|
|
2013-08-30 07:52:03 +00:00
|
|
|
* Fri Aug 30 2013 Paolo Bonzini <pbonzini@redhat.com> - 20130515svn14365-6
|
|
|
|
|
- Revert previous change; firmware packages should be noarch, and building
|
|
|
|
|
BaseTools twice is simply wrong.
|
|
|
|
|
|
2013-08-19 16:24:02 +00:00
|
|
|
* Mon Aug 19 2013 Kay Sievers <kay@redhat.com> - 20130515svn14365-5
|
|
|
|
|
- Add sub-package with EFI shell
|
|
|
|
|
|
2013-08-03 09:22:44 +00:00
|
|
|
* Sat Aug 03 2013 Fedora Release Engineering <rel-eng@lists.fedoraproject.org> - 20130515svn14365-4
|
|
|
|
|
- Rebuilt for https://fedoraproject.org/wiki/Fedora_20_Mass_Rebuild
|
|
|
|
|
|
2013-05-23 06:16:31 +00:00
|
|
|
* Thu May 23 2013 Dan Horák <dan[at]danny.cz> 20130515svn14365-3
|
|
|
|
|
- set ExclusiveArch
|
|
|
|
|
|
2013-05-02 12:46:06 +00:00
|
|
|
* Thu May 16 2013 Paolo Bonzini <pbonzini@redhat.com> 20130515svn14365-2
|
|
|
|
|
- Fix edk2-tools-python Requires
|
|
|
|
|
|
|
|
|
|
* Wed May 15 2013 Paolo Bonzini <pbonzini@redhat.com> 20130515svn14365-1
|
|
|
|
|
- Split edk2-tools-doc and edk2-tools-python
|
|
|
|
|
- Fix Python BuildRequires
|
|
|
|
|
- Remove FatBinPkg at package creation time.
|
|
|
|
|
- Use fully versioned dependency.
|
|
|
|
|
- Add comment on how to generate the sources.
|
|
|
|
|
|
|
|
|
|
* Thu May 2 2013 Paolo Bonzini <pbonzini@redhat.com> 20130502.g732d199-1
|
|
|
|
|
- Create.
|
