Re: [edk2] [PATCH v2 4/8] OvmfPkg: introduce FlashNvStorageAddressLib

2017-12-01 Thread Laszlo Ersek
On 12/01/17 12:03, Laszlo Ersek wrote: > On 12/01/17 09:55, Ard Biesheuvel wrote: >> On 30 November 2017 at 16:30, Laszlo Ersek wrote: >>> An OVMF binary built with >>> >>> -D SMM_REQUIRE >>> >>> or with >>> >>> -D MEM_VARSTORE_EMU_ENABLE=FALSE >>> >>> requires flash to be present at the expec

Re: [edk2] [PATCH v2 4/8] OvmfPkg: introduce FlashNvStorageAddressLib

2017-12-01 Thread Laszlo Ersek
On 12/01/17 09:55, Ard Biesheuvel wrote: > On 30 November 2017 at 16:30, Laszlo Ersek wrote: >> An OVMF binary built with >> >> -D SMM_REQUIRE >> >> or with >> >> -D MEM_VARSTORE_EMU_ENABLE=FALSE >> >> requires flash to be present at the expected (build-time determined) >> location; falling ba

Re: [edk2] [PATCH v2 4/8] OvmfPkg: introduce FlashNvStorageAddressLib

2017-12-01 Thread Ard Biesheuvel
On 30 November 2017 at 16:30, Laszlo Ersek wrote: > An OVMF binary built with > > -D SMM_REQUIRE > > or with > > -D MEM_VARSTORE_EMU_ENABLE=FALSE > > requires flash to be present at the expected (build-time determined) > location; falling back to the emulated varstore is not possible. > > In s

[edk2] [PATCH v2 4/8] OvmfPkg: introduce FlashNvStorageAddressLib

2017-11-30 Thread Laszlo Ersek
An OVMF binary built with -D SMM_REQUIRE or with -D MEM_VARSTORE_EMU_ENABLE=FALSE requires flash to be present at the expected (build-time determined) location; falling back to the emulated varstore is not possible. In such builds, we can replace the settings of the - varstore, - FTW worki