mirror of https://github.com/acidanthera/audk.git
578a715cfc
Flash can be write-protected in qemu (which is usually the case for code). In case the variable store flash block is configured read-only ovmf wouldn't be able to store EFI variables there, so not setting up fvb in that case (and fallhack to emulation) is the better option. It'll avoid problems later due to flash writes failing. The patch tries to write back the original value read earlier, so flash content doesn't change in case the write succeeds. But the status we read back after the attempt to write will tell us whenever flash is writable or not. Signed-off-by: Gerd Hoffmann <kraxel@redhat.com> |
||
|---|---|---|
| .. | ||
| FvbInfo.c | ||
| FvbServicesRuntimeDxe.inf | ||
| FvbServicesSmm.inf | ||
| FwBlockService.c | ||
| FwBlockService.h | ||
| FwBlockServiceDxe.c | ||
| FwBlockServiceSmm.c | ||
| QemuFlash.c | ||
| QemuFlash.h | ||
| QemuFlashDxe.c | ||
| QemuFlashSmm.c | ||