From f527942e6bdd9f198db90f2de99a0482e9be5b1b Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Antoine=20C=C5=93ur?= Date: Tue, 9 Jul 2019 17:10:11 +0800 Subject: FmpDevicePkg: Fix various typos MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Fix one typo in FmpDevicePkg. Signed-off-by: Cœur Reviewed-by: Star Zeng Reviewed-by: Chasel Chiu --- IntelFsp2Pkg/FspSecCore/Ia32/FspApiEntryM.nasm | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'IntelFsp2Pkg/FspSecCore/Ia32/FspApiEntryM.nasm') diff --git a/IntelFsp2Pkg/FspSecCore/Ia32/FspApiEntryM.nasm b/IntelFsp2Pkg/FspSecCore/Ia32/FspApiEntryM.nasm index f14c18c7b9..e7261b41cd 100644 --- a/IntelFsp2Pkg/FspSecCore/Ia32/FspApiEntryM.nasm +++ b/IntelFsp2Pkg/FspSecCore/Ia32/FspApiEntryM.nasm @@ -194,9 +194,9 @@ StackSetupDone: ; ; Pass BFV into the PEI Core - ; It uses relative address to calucate the actual boot FV base + ; It uses relative address to calculate the actual boot FV base ; For FSP implementation with single FV, PcdFspBootFirmwareVolumeBase and - ; PcdFspAreaBaseAddress are the same. For FSP with mulitple FVs, + ; PcdFspAreaBaseAddress are the same. For FSP with multiple FVs, ; they are different. The code below can handle both cases. ; call ASM_PFX(AsmGetFspBaseAddress) -- cgit v1.2.3