sravan/system76-edk2
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

OvmfPkg/Qemu: Fix various typos

Browse Source 
Fix various typos in comments and documentation.

When "VbeShim.asm" is modified, we have to re-run "VbeShim.sh"
to update "VbeShim.h".
The string modified by this patch is only used when the DEBUG
macro (at the top of the file) is commented out. Since the
string is not referenced, NASM eliminates it, resulting in
the same byte array content in "VbeShim.h".

Cc: Jordan Justen <jordan.l.justen@intel.com>
Cc: Laszlo Ersek <lersek@redhat.com>
Cc: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Signed-off-by: Antoine Coeur <coeur@gmx.fr>
Reviewed-by: Philippe Mathieu-Daude <philmd@redhat.com>
Reviewed-by: Laszlo Ersek <lersek@redhat.com>
Signed-off-by: Philippe Mathieu-Daude <philmd@redhat.com>
Message-Id: <20200207010831.9046-58-philmd@redhat.com>
This commit is contained in:
Antoine Coeur
2020-02-07 02:08:10 +01:00
committed by mergify[bot]
parent f6fc95c943
commit a2e7559576
11 changed files with 25 additions and 25 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
OvmfPkg/QemuFlashFvbServicesRuntimeDxe/FvbInfo.c
View File

@@ -21,7 +21,7 @@
#include <Pi/PiFirmwareVolume.h>
//
// The protocols, PPI and GUID defintions for this module
// The protocols, PPI and GUID definitions for this module
//
#include <Guid/SystemNvDataGuid.h>
//
@@ -41,7 +41,7 @@ typedef struct {
EFI_FVB_MEDIA_INFO mPlatformFvbMediaInfo[] = {
//
// Systen NvStorage FVB
// System NvStorage FVB
//
{
FixedPcdGet32 (PcdFlashNvStorageVariableSize) +

4
OvmfPkg/QemuFlashFvbServicesRuntimeDxe/FvbServicesRuntimeDxe.inf
View File

@@ -1,8 +1,8 @@
## @file
# Component description file for QEMU Flash Fimware Volume Block DXE driver
# Component description file for QEMU Flash Firmware Volume Block DXE driver
# module.
#
# This DXE runtime driver implements and produces the Fimware Volue Block
# This DXE runtime driver implements and produces the Firmware Volue Block
# Protocol for a QEMU flash device.
#
# Copyright (c) 2006 - 2013, Intel Corporation. All rights reserved.<BR>

4
OvmfPkg/QemuFlashFvbServicesRuntimeDxe/FvbServicesSmm.inf
View File

@@ -1,8 +1,8 @@
## @file
# Component description file for QEMU Flash Fimware Volume Block SMM driver
# Component description file for QEMU Flash Firmware Volume Block SMM driver
# module.
#
# This SMM driver implements and produces the SMM Fimware Volue Block Protocol
# This SMM driver implements and produces the SMM Firmware Volue Block Protocol
# for a QEMU flash device.
#
# Copyright (C) 2015, Red Hat, Inc.

8
OvmfPkg/QemuFlashFvbServicesRuntimeDxe/FwBlockService.c
View File

@@ -15,7 +15,7 @@
**/
//
// The protocols, PPI and GUID defintions for this module
// The protocols, PPI and GUID definitions for this module
//
#include <Protocol/DevicePath.h>
#include <Protocol/FirmwareVolumeBlock.h>
@@ -118,7 +118,7 @@ GetFvbInstance (
returned
Global - Pointer to ESAL_FWB_GLOBAL that contains all
instance data
FwhInstance - The EFI_FW_VOL_INSTANCE fimrware instance structure
FwhInstance - The EFI_FW_VOL_INSTANCE firmware instance structure
Returns:
EFI_SUCCESS - Successfully returns
@@ -695,7 +695,7 @@ FvbProtocolWrite (
Writes data beginning at Lba:Offset from FV. The write terminates either
when *NumBytes of data have been written, or when a block boundary is
reached. *NumBytes is updated to reflect the actual number of bytes
written. The write opertion does not include erase. This routine will
written. The write operation does not include erase. This routine will
attempt to write only the specified bytes. If the writes do not stick,
it will return an error.
@@ -740,7 +740,7 @@ FvbProtocolRead (
Reads data beginning at Lba:Offset from FV. The Read terminates either
when *NumBytes of data have been read, or when a block boundary is
reached. *NumBytes is updated to reflect the actual number of bytes
written. The write opertion does not include erase. This routine will
written. The write operation does not include erase. This routine will
attempt to write only the specified bytes. If the writes do not stick,
it will return an error.