Re: [edk2-devel] one possible issue with ovmf fvb

2021-11-29 Thread Gerd Hoffmann
Hi, > On real X64 hardware you can’t be in 64-bit mode without pageables, > and you can’t put pageables in the ROM. Thus PEI ends up being IA32 > (i386) and this usually means the DXE Core gets loaded < 4 GiB, and > the initial memory map for DXE is memory < 4 GiB. Well, to exact there are two

Re: [edk2-devel] one possible issue with ovmf fvb

2021-11-27 Thread Andrew Fish via groups.io
> On Nov 25, 2021, at 4:43 AM, maobibo wrote: > > Hi Gerd, > > I am porting Loongarch Qemu uefi bios, and I want to use reuse ovmf code. > And I encounter one problem > when using OvmfPkg/EmuVariableFvbRuntimeDxe/Fvb.c > > here is piece of code: > -

Re: [edk2-devel] one possible issue with ovmf fvb

2021-11-27 Thread maobibo
On 11/25/2021 06:38 PM, Gerd Hoffmann wrote: > Hi, > >> PcdStatus = PcdSet64S (PcdFlashNvStorageVariableBase64, (UINT32)(UINTN) >> Ptr); >> ASSERT_RETURN_ERROR (PcdStatus); > > I guess you are referring to that UINT32 cast? > Not sure why it is there. I think you can just drop it. Yes,

[edk2-devel] one possible issue with ovmf fvb

2021-11-27 Thread maobibo
Hi Gerd, I am porting Loongarch Qemu uefi bios, and I want to use reuse ovmf code. And I encounter one problem when using OvmfPkg/EmuVariableFvbRuntimeDxe/Fvb.c here is piece of code: --- Initialize = TRUE; if (PcdGet64 (PcdEmuVaria

Re: [edk2-devel] one possible issue with ovmf fvb

2021-11-25 Thread Gerd Hoffmann
Hi, > PcdStatus = PcdSet64S (PcdFlashNvStorageVariableBase64, (UINT32)(UINTN) > Ptr); > ASSERT_RETURN_ERROR (PcdStatus); I guess you are referring to that UINT32 cast? Not sure why it is there. I think you can just drop it. > Can uefi bios manage memory beyond 4G? The X64 builds can do