From: "Grzegorz Bernacki" <gjb@semihalf.com>
To: devel@edk2.groups.io
Cc: leif@nuviainc.com, ardb+tianocore@kernel.org,
Samer.El-Haj-Mahmoud@arm.com, sunny.Wang@arm.com,
mw@semihalf.com, upstream@semihalf.com, jiewen.yao@intel.com,
jian.j.wang@intel.com, min.m.xu@intel.com, lersek@redhat.com,
sami.mujawar@arm.com, afish@apple.com, ray.ni@intel.com,
jordan.l.justen@intel.com, rebecca@bsdio.com, grehan@freebsd.org,
thomas.abraham@arm.com, chasel.chiu@intel.com,
nathaniel.l.desimone@intel.com, gaoliming@byosoft.com.cn,
eric.dong@intel.com, michael.d.kinney@intel.com,
zailiang.sun@intel.com, yi.qian@intel.com, graeme@nuviainc.com,
rad@semihalf.com, pete@akeo.ie,
Grzegorz Bernacki <gjb@semihalf.com>
Subject: [PATCH v4 2/8] ArmVirtPkg: add SecureBootVariableLib class resolution
Date: Wed, 30 Jun 2021 14:34:02 +0200 [thread overview]
Message-ID: <20210630123412.996158-3-gjb@semihalf.com> (raw)
In-Reply-To: <20210630123412.996158-1-gjb@semihalf.com>
The edk2 patch
SecurityPkg: Create library for setting Secure Boot variables.
removes generic functions from SecureBootConfigDxe and places
them into SecureBootVariableLib. This patch adds SecureBootVariableLib
mapping for ArmVirtPkg platform.
Signed-off-by: Grzegorz Bernacki <gjb@semihalf.com>
---
ArmVirtPkg/ArmVirt.dsc.inc | 1 +
1 file changed, 1 insertion(+)
diff --git a/ArmVirtPkg/ArmVirt.dsc.inc b/ArmVirtPkg/ArmVirt.dsc.inc
index d9abadbe70..11c1f53537 100644
--- a/ArmVirtPkg/ArmVirt.dsc.inc
+++ b/ArmVirtPkg/ArmVirt.dsc.inc
@@ -168,6 +168,7 @@
#
!if $(SECURE_BOOT_ENABLE) == TRUE
AuthVariableLib|SecurityPkg/Library/AuthVariableLib/AuthVariableLib.inf
+ SecureBootVariableLib|SecurityPkg/Library/SecureBootVariableLib/SecureBootVariableLib.inf
# re-use the UserPhysicalPresent() dummy implementation from the ovmf tree
PlatformSecureLib|OvmfPkg/Library/PlatformSecureLib/PlatformSecureLib.inf
--
2.25.1
next prev parent reply other threads:[~2021-06-30 12:34 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-30 12:34 [PATCH v4 0/12] Secure Boot default keys Grzegorz Bernacki
2021-06-30 12:34 ` [PATCH v4 1/8] SecurityPkg: Create library for setting Secure Boot variables Grzegorz Bernacki
2021-06-30 12:34 ` Grzegorz Bernacki [this message]
2021-06-30 17:08 ` [PATCH v4 2/8] ArmVirtPkg: add SecureBootVariableLib class resolution Laszlo Ersek
2021-06-30 12:34 ` [PATCH v4 3/8] Intel Platforms: " Grzegorz Bernacki
2021-06-30 12:34 ` [PATCH v4 4/8] ArmPlatformPkg: Create include file for default key content Grzegorz Bernacki
2021-06-30 12:34 ` [PATCH v4 5/8] SecurityPkg: Add SecureBootDefaultKeysDxe driver Grzegorz Bernacki
2021-06-30 12:34 ` [PATCH v4 6/8] SecurityPkg: Add EnrollFromDefaultKeys application Grzegorz Bernacki
2021-06-30 12:34 ` [PATCH v4 7/8] SecurityPkg: Add new modules to Security package Grzegorz Bernacki
2021-06-30 12:34 ` [PATCH v4 8/8] SecurityPkg: Add option to reset secure boot keys Grzegorz Bernacki
2021-06-30 12:34 ` [edk2-platforms PATCH v4 09/12] Intel Platforms: add SecureBootVariableLib class resolution Grzegorz Bernacki
2021-06-30 12:34 ` [edk2-platforms PATCH v4 10/12] ARM Silicon and " Grzegorz Bernacki
2021-06-30 13:26 ` Graeme Gregory
2021-06-30 12:34 ` [edk2-platforms PATCH v4 11/12] RISC-V " Grzegorz Bernacki
2021-07-01 3:50 ` [edk2-devel] " Abner Chang
2021-07-01 5:43 ` Daniel Schaefer
2021-06-30 12:34 ` [edk2-platforms PATCH v4 12/12] Platform/RaspberryPi: Enable default Secure Boot variables initialization Grzegorz Bernacki
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-list 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=20210630123412.996158-3-gjb@semihalf.com \
--to=devel@edk2.groups.io \
/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