Bill Paul [mailto:wp...@windriver.com] wrote:
]The other day I decided fix my code so that it could build with the EDKII on
]Windows without a GNU toolchain (which meant re-writing some assembly from GNU
]AT&T syntax to Intel syntax -- don't ask), so I looked through the "supported
]toolchains
Hello limming
Ahh emulator and not fdf files. Thanks I'll try that. I appreciate your
expertise.
John
On Feb 7, 2014 5:45 PM, "Gao, Liming" wrote:
> John:
>
>Your step 9 edits EmulatorPkg.fdf to include MyDriverSample. But, no
> step edits Nt32Pkg.fdf to include it. So, you can't see it NT
John:
Your step 9 edits EmulatorPkg.fdf to include MyDriverSample. But, no step
edits Nt32Pkg.fdf to include it. So, you can't see it NT32 FV Output folder.
Thanks
Liming
From: John Davis [mailto:davi...@gmail.com]
Sent: Saturday, February 08, 2014 6:49 AM
To: edk2-devel@lists.sourceforge.net
Good comments. Yes. We will fix them.
-Original Message-
From: Alexei Fedorov [mailto:alexei.fedo...@arm.com]
Sent: Thursday, January 30, 2014 7:15 PM
To: edk2-devel@lists.sourceforge.net
Subject: Re: [edk2] Bug in TerminalDxe UnicodeFiFoRemoveOneKey() function
Liming,
I didn't hit any
I can confirm this happens with VS 2012 and DDK 7.1.
Em 07/02/2014 20:14, "Jordan Justen" escreveu:
> On Wed, Feb 5, 2014 at 1:22 PM, Mauro Faccenda wrote:
> > The BOOLEAN IsFinal variable initialization isn't properly made by
> > MSVC, to make it compile OVMF the variable needs to be initializ
Hello bill
This might not help but once a long time ago I had built a driver using the
ddk and a user stack using the SDK. Both of these were free.
Later when I tried to integrate it with a larger component built using a
devstudio app the app failed to use the use mode stack DLLs I had built
wit
The other day I decided fix my code so that it could build with the EDKII on
Windows without a GNU toolchain (which meant re-writing some assembly from GNU
AT&T syntax to Intel syntax -- don't ask), so I looked through the "supported
toolchains" list in tools_def.txt to see what that would entai
From: Laszlo Ersek
This driver (from
"MdeModulePkg/Universal/Acpi/BootScriptExecutorDxe/BootScriptExecutorDxe.inf")
is first loaded normally during DXE. When the
EFI_DXE_SMM_READY_TO_LOCK_PROTOCOL is installed by any DXE driver (purely
as a form of notification), the driver reloads itself to rese
From: Laszlo Ersek
"MdeModulePkg/Universal/Acpi/S3SaveStateDxe/S3SaveStateDxe.inf" produces
the EFI_S3_SAVE_STATE_PROTOCOL which allows creation and saving of an S3
Boot Script, to be replayed in PEI during S3 Resume. The script contains
opcodes and opcode arguments to configure CPU, PCI and IO r
This 32k section of RAM will be declared to the PEI Core on
S3 resume to allow memory allocations during S3 resume PEI.
If the boot mode is BOOT_ON_S3_RESUME, then we publish
the pre-reserved PcdS3AcpiReservedMemory range to PEI.
If the boot mode is not BOOT_ON_S3_RESUME, then we reserve
this ran
From: Laszlo Ersek
Such a packaged query function will come in handy in the following
patches.
Contributed-under: TianoCore Contribution Agreement 1.0
Signed-off-by: Laszlo Ersek
Reviewed-by: Jordan Justen
[jordan.l.jus...@intel.com: check for enabled rather than disabled]
Contributed-under: T
From: Laszlo Ersek
Contributed-under: TianoCore Contribution Agreement 1.0
Signed-off-by: Laszlo Ersek
[jordan.l.jus...@intel.com: move to MemDetect.c; use PCDs]
Contributed-under: TianoCore Contribution Agreement 1.0
Signed-off-by: Jordan Justen
---
OvmfPkg/PlatformPei/MemDetect.c | 11 ++
From: Laszlo Ersek
"OvmfPkg/AcpiS3SaveDxe/AcpiS3SaveDxe.inf" (originally:
"IntelFrameworkModulePkg/Universal/Acpi/AcpiS3SaveDxe/AcpiS3SaveDxe.inf")
produces the EFI_ACPI_S3_SAVE_PROTOCOL.
When found, this protocol is automatically invoked by
BdsLibBootViaBootOption(), in file
"IntelFrameworkModu
From: Laszlo Ersek
The S3 suspend/resume infrastructure depends on the LockBox library class.
The edk2 tree currently contains Null and SMM instances. The Null instance
is useless, and the SMM instance would require SMM emulation by including
the SMM core and adding several new drivers, which is
From: Laszlo Ersek
"IntelFrameworkModulePkg/Universal/Acpi/AcpiS3SaveDxe/AcpiS3SaveDxe.inf"
currently specifies a DepEx on gEfiMpServiceProtocolGuid (MP Services).
The justification is the following code sequence:
InstallAcpiS3Save()
if PcdFrameworkCompatibilitySupport is set:
Insta
Since we marked the FV at PcdOvmfPeiMemFvBase as ACPI NVS memory,
we can use it on S3 resume.
The FV at PcdOvmfDxeMemFvBase may have been overwritten by the OS,
but we do not use it's contents on S3 resume.
Contributed-under: TianoCore Contribution Agreement 1.0
Signed-off-by: Jordan Justen
Revi
From: Laszlo Ersek
On X64, the reset vector code in
"OvmfPkg/ResetVector/Ia32/PageTables64.asm" identity maps the first 4GB of
RAM for PEI, consuming six frames starting at 8MB.
This range is declared by the PcdOvmfSecPageTablesBase/Size PCDs.
Contributed-under: TianoCore Contribution Agreement
From: Laszlo Ersek
BootScriptExecutorDxe, to be pulled in in the next patch, was written with
the SMM implementation of LockBox in mind. That implementation is split in
the following three parts:
- client side (DXE/PEI) library,
- SMM driver producing gEfiLockBoxProtocolGuid,
- driver side (SMM)
v5 of Laszlo's S3 series
v5:
* The FV restructure sub-set of v4 was committed
to the tree, so it is now gone in v5
* This version now should not break Xen's
normal boot path. (But, Xen will not support
S3 resume until we add a path that sets
PlatformPei's mS3Supported for Xen.)
* If
From: Laszlo Ersek
Data is transferred between S3 Suspend and S3 Resume as follows:
S3 Suspend (DXE):
(1) BdsLibBootViaBootOption()
EFI_ACPI_S3_SAVE_PROTOCOL [AcpiS3SaveDxe]
- saves ACPI S3 Context to LockBox -+
(including FACS address -- FACS ACPI table
We will not be running DXE on S3 resume, so we don't
need to do these initialization items:
* Reserve EMU Variable memory range
* Declare Firmware volumes
* Add memory HOBs
v5:
* Move MiscInitialization back to running on S3 resume
Contributed-under: TianoCore Contribution Agreement 1.0
Signe
On S3 resume, we skip decompression of the PEI FV, and expect
to jump directly into it. For this to work, we need the OS to
leave the memory range untouched.
Contributed-under: TianoCore Contribution Agreement 1.0
Signed-off-by: Jordan Justen
---
OvmfPkg/PlatformPei/Fv.c | 5 +++--
1 file change
From: Laszlo Ersek
The trigger to actually save the boot script is the installation of
EFI_DXE_SMM_READY_TO_LOCK_PROTOCOL, to be performed by any DXE driver.
Installation of the protocol also locks down SMM (as its name indicates)
and (in theory) prevents further LockBox access.
We cannot instal
Contributed-under: TianoCore Contribution Agreement 1.0
Signed-off-by: Jordan Justen
---
OvmfPkg/PlatformPei/Platform.c | 10 +-
OvmfPkg/PlatformPei/Platform.h | 2 ++
2 files changed, 7 insertions(+), 5 deletions(-)
diff --git a/OvmfPkg/PlatformPei/Platform.c b/OvmfPkg/PlatformPei/Plat
From: Laszlo Ersek
"UefiCpuPkg/Universal/Acpi/S3Resume2Pei/S3Resume2Pei.inf" produces the
EFI_PEI_S3_RESUME2 PEIM-to-PEIM Interface.
When the platform-specific initialization code (in PEI) sets the Boot Mode
to BOOT_ON_S3_RESUME, the DXE IPL (which is the last step in PEI) skips
the DXE phase en
This is needed for BootScriptExecutorDxe.
Contributed-under: TianoCore Contribution Agreement 1.0
Signed-off-by: Jordan Justen
---
OvmfPkg/OvmfPkgIa32.dsc| 5 -
OvmfPkg/OvmfPkgIa32X64.dsc | 5 -
OvmfPkg/OvmfPkgX64.dsc | 5 -
3 files changed, 12 insertions(+), 3 deletions(-)
QEMU indicates whether S3 is supported or not in the
fw-cfg interface.
Contributed-under: TianoCore Contribution Agreement 1.0
Signed-off-by: Jordan Justen
---
OvmfPkg/PlatformPei/Platform.c | 8
OvmfPkg/PlatformPei/Platform.h | 2 ++
OvmfPkg/PlatformPei/PlatformPei.inf | 1 +
On Wed, Feb 5, 2014 at 1:22 PM, Mauro Faccenda wrote:
> The BOOLEAN IsFinal variable initialization isn't properly made by
> MSVC, to make it compile OVMF the variable needs to be initialized.
Which version of MSVC flagged this?
Thanks for the contribution!
Reviewed-by: Jordan Justen
> Contri
Hello Andrew,
At first I was like yay, then I noticed in step 9 I had edited the .fdf
file to include MyDriverSample.
FWIW, I do have a MyDriverSample in the ..FV\Guid.xref file. I even have
MyDriverSample.efi in DEBUG_VS2010x86/IA32 folder.
Its just not in the fv folder.
John
---
On Feb 7, 2014, at 2:03 PM, John Davis wrote:
> Hello
>
> I am trying to build a copy of DriverSampleDxe. This is the process I am
> using. The build completes and I see it building MyDriverSampleDxe.
> However, when I examine the
> C:\fw\edk2\Build\NT32IA32\DEBUG_VS2010x86\FV\Ffs directo
Hello
I am trying to build a copy of DriverSampleDxe. This is the process I am
using. The build completes and I see it building MyDriverSampleDxe.
However, when I examine the
C:\fw\edk2\Build\NT32IA32\DEBUG_VS2010x86\FV\Ffs directory I don't see a
GUIDMyDriverSample folder.
--
This is the
Maybe this will help somebody. I made it while trying to work from build
output in reverse.
I examined the final .fv output and then created a table pointing back to
the source directory for each of the components in an NT32 emulator build.
https://sourceforge.net/p/uefinotes/wiki/FV%20Sources/
Hi
As i'm working in UEFI domain i want to post my queries in this forum.
How to put my questions and get answers in this
edk2-d...@lists.souceforge.net.
I'm getting updates from this edk2-d...@lists.souceforge.net site. but i
dont know how to put my queries.
--
Thanks in advance,
Prem.
On F
33 matches
Mail list logo
