Re: [edk2] [PATCH] OvmfPkg/PlatformBootManagerLib: remove stale FvFile boot options

2016-07-12 Thread Laszlo Ersek
On 07/12/16 04:36, Ni, Ruiyu wrote: > Laszlo, > OVMF uses old style of FV device path node: MemoryMapped(...). > If you check Nt32Pkg/Nt32Pkg.fdf, there is FvNameGuid field under[FV] section. > - > [FV.FvRecovery] > .. > FvNameGuid = 6D99E806-3D38-42c2-A095-5F4300BFD7DC > > >

Re: [edk2] [PATCH] OvmfPkg/PlatformBootManagerLib: remove stale FvFile boot options

2016-07-11 Thread Ni, Ruiyu
Laszlo, OVMF uses old style of FV device path node: MemoryMapped(...). If you check Nt32Pkg/Nt32Pkg.fdf, there is FvNameGuid field under[FV] section. - [FV.FvRecovery] .. FvNameGuid = 6D99E806-3D38-42c2-A095-5F4300BFD7DC If you add FvNameGuid field under [FV] section for OVMF,

[edk2] [PATCH] OvmfPkg/PlatformBootManagerLib: remove stale FvFile boot options

2016-07-11 Thread Laszlo Ersek
Changing the base address or the size of DXEFV, changing PcdShellFile, or omitting the UEFI Shell from the OVMF binary, all lead to "EFI Internal Shell" boot options that are technically different from each other and do not describe any built-in shell binary exactly. Such options can accumulate in