From: Stefan Reiter <s.reiter@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [RFC v2 edk2-firmware 1/4] enable TPM and TPM2 support
Date: Thu, 23 Sep 2021 16:54:56 +0200 [thread overview]
Message-ID: <20210923145459.1508558-2-s.reiter@proxmox.com> (raw)
In-Reply-To: <20210923145459.1508558-1-s.reiter@proxmox.com>
Necessary for an OS to use a TPM attached to a OVMF VM.
Signed-off-by: Stefan Reiter <s.reiter@proxmox.com>
---
debian/rules | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/debian/rules b/debian/rules
index fb85b29..ece77be 100755
--- a/debian/rules
+++ b/debian/rules
@@ -54,6 +54,8 @@ build-ovmf: setup-build
-a $(EDK2_HOST_ARCH) \
-t $(EDK2_TOOLCHAIN) \
-DSECURE_BOOT_ENABLE=FALSE \
+ -DTPM_ENABLE=TRUE \
+ -DTPM2_ENABLE=TRUE \
-DFD_SIZE_2MB \
-n $$(getconf _NPROCESSORS_ONLN)
@@ -75,6 +77,8 @@ build-qemu-efi: setup-build
-p ArmVirtPkg/ArmVirtQemu.dsc \
-DHTTP_BOOT_ENABLE=TRUE \
-DSECURE_BOOT_ENABLE=FALSE \
+ -DTPM_ENABLE=TRUE \
+ -DTPM2_ENABLE=TRUE \
-DINTEL_BDS \
-b RELEASE
dd if=/dev/zero of=Build/ArmVirtQemu-$(EDK2_HOST_ARCH)/RELEASE_$(EDK2_TOOLCHAIN)/FV/$(FW_NAME)_CODE.fd bs=1M seek=64 count=0
--
2.30.2
next prev parent reply other threads:[~2021-09-23 14:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-23 14:54 [pve-devel] [RFC v2 0/4] Initial TPM support for VMs Stefan Reiter
2021-09-23 14:54 ` Stefan Reiter [this message]
2021-09-23 15:07 ` [pve-devel] applied: [RFC v2 edk2-firmware 1/4] enable TPM and TPM2 support Thomas Lamprecht
2021-09-23 14:54 ` [pve-devel] [RFC v2 storage 2/4] import: don't check for 1K aligned size Stefan Reiter
2021-09-23 14:54 ` [pve-devel] [RFC v2 qemu-server 3/4] fix #3075: add TPM v1.2 and v2.0 support via swtpm Stefan Reiter
2021-09-23 14:54 ` [pve-devel] [RFC v2 manager 4/4] ui: add support for adding TPM devices Stefan Reiter
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=20210923145459.1508558-2-s.reiter@proxmox.com \
--to=s.reiter@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
/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