mirror of https://github.com/acidanthera/audk.git
582085eb1f
The ValidateFvHeader() function checks several conditions against the firmware volume header. Failure of the first of these checks, reported as "No Firmware Volume header present", is a common situation for unformatted flash images, especially when a new virtual machine is created. Similarly, "Variable Store Guid non-compatible" is common when the firmware binary is switched from Secure Boot-incapable to Secure Boot-capable, or vice versa. The only caller of ValidateFvHeader(), NorFlashFvbInitialize(), handles all these mismatches by installing a new FVB header. It also emits another, loud ERROR message (which is even less justified when it is triggered by (BootMode == BOOT_WITH_DEFAULT_SETTINGS)). Downgrade these messages from EFI_D_ERROR to EFI_D_INFO, so that they don't clutter the debug output when the PcdDebugPrintErrorLevel mask only enables EFI_D_ERROR (i.e., in a "silent" build). These messages have annoyed / confused users; see for example: - https://bugzilla.redhat.com/show_bug.cgi?id=1270279 - http://thread.gmane.org/gmane.comp.bios.edk2.devel/2772/focus=2869 Cc: Leif Lindholm <leif.lindholm@linaro.org> Cc: Ard Biesheuvel <ard.biesheuvel@linaro.org> Cc: Drew Jones <drjones@redhat.com> Cc: Yehuda Yitschak <yehuday@marvell.com> Contributed-under: TianoCore Contribution Agreement 1.0 Signed-off-by: Laszlo Ersek <lersek@redhat.com> Reviewed-by: Leif Lindholm <leif.lindholm@linaro.org> git-svn-id: https://svn.code.sf.net/p/edk2/code/trunk/edk2@18618 6f19259b-4bc3-4df7-8a09-765794883524 |
||
|---|---|---|
| .. | ||
| ArmJunoPkg | ||
| ArmVExpressPkg | ||
| Bds | ||
| Documentation | ||
| Drivers | ||
| FileSystem/BootMonFs | ||
| Include | ||
| Library | ||
| MemoryInitPei | ||
| PlatformPei | ||
| PrePeiCore | ||
| PrePi | ||
| Scripts | ||
| Sec | ||
| ArmPlatformPkg-2ndstage.dsc | ||
| ArmPlatformPkg-2ndstage.fdf | ||
| ArmPlatformPkg.dec | ||
| ArmPlatformPkg.dsc | ||
| ArmPlatformPkg.fdf | ||
| Contributions.txt | ||
| License.txt | ||