On Nov 6, 2013, at 11:34 PM, Gao, Liming wrote:
> Andrew:
> EDKII build system bases on file postfix name to handle them. For new
> postfix name, you may extend build_rule.txt file to add new rule for it.
>
I know that I can chain via names, but this does not solve issues with parallel
bui
Andrew:
EDKII build system bases on file postfix name to handle them. For new postfix
name, you may extend build_rule.txt file to add new rule for it.
Thanks
Liming
-Original Message-
From: Andrew Fish [mailto:af...@apple.com]
Sent: Thursday, November 07, 2013 11:54 AM
To: edk2-buildt
Mars:
PeiMain uses PpiData->NotifyListEnd and DispatchListEnd index to
differentiate NotifyPpi with CallBack and Dispatch mode.
The range between NofiyListEnd and DispatchListEnd are for NotifyPpi with
CallBack mode.
The range between DispatchListEnd and EndOfPpiListPtrs are for NotifyPpi
I’d like like to have an INF file that is full of *.XYZ files that get run
through the C pre-processor and converted to an intermediate form. I would like
to take set of intermediate files and post process them info a single .bin file
that will then end up in an FFS file.
What is the best way
The 1MB image with full debug and the shell included is too
large to implement flash based non-volatile variable.
After this change, building with -D FD_SIZE_1MB will
force the smaller flash size.
The default size for RELEASE build remains at 1MB, so using
-b RELEASE on the build command line wil
https://github.com/jljusten/edk2.git ovmf-nvvars-v2
This series implements support for QEMU's emulated
system flash.
This allows for persistent UEFI non-volatile variables.
Previously we attempted to emulate non-volatile
variables in a few ways, but each of them would fail
in particular situatio
Contributed-under: TianoCore Contribution Agreement 1.0
Signed-off-by: Jordan Justen
---
OvmfPkg/README | 37 +
1 file changed, 37 insertions(+)
diff --git a/OvmfPkg/README b/OvmfPkg/README
index 213d864..4cec351 100644
--- a/OvmfPkg/README
+++ b/OvmfPkg/REA
This is to prepare for QEMU flash support which will allow
non-volatile variables to be saved in the flash image.
Note two size changes:
* NV Varstore size increased from 0xc000 to 0xe000
* FTW work size decreased from 0x2000 to 0x1000
The reason for this change is that the fault-tolerant write
This driver will support a flash FVB implementation if QEMU flash
is detected.
The driver is added to the apriori list to make sure it runs
before the EmuVariableFvbRuntimeDxe driver. If this driver detects
flash support, then it will disable the EmuVariableFvbRuntimeDxe
driver by setting PcdFlash
If the QEMU version is found to be >= 1.6, then automatically
enable flash (using the QEMU pflash command line parameter).
QEMU supports flash since 1.2, but only if KVM is disabled.
As of QEMU 1.6, flash support should also be enabled when
KVM is used. Therefore it is safest to only enable flash
In a later patch we will want to mark the flash memory as a
runtime services data memory range. This will allow a new runtime
services firmware block driver to read & write flash memory when
the OS has set up virtual memory protection.
Since this memory range will appear as runtime services data,
Contributed-under: TianoCore Contribution Agreement 1.0
Signed-off-by: Jordan Justen
Reviewed-by: Laszlo Ersek
---
OvmfPkg/OvmfPkg.dec | 12 +++-
1 file changed, 11 insertions(+), 1 deletion(-)
diff --git a/OvmfPkg/OvmfPkg.dec b/OvmfPkg/OvmfPkg.dec
index d874f0c..01fe469 100644
--- a/
If QEMU flash is supported, then the PcdFlashNvStorageVariableBase64
will be set by the flash FVB driver. If it is set to a non-zero value,
then we disable memory based variables.
In future patches we will add the flash FVB driver and
force it to run before this driver. Therefore, if QEMU flash
wr
If this argument is used, then when QEMU is run, the -pflash
parameter will be used with QEMU to enable QEMU's flash
mode.
It should be used before the 'qemu' argument, since it is
not a QEMU parameter, but instead it updates how build.sh
runs QEMU.
Contributed-under: TianoCore Contribution Agree
On Wed, Nov 6, 2013 at 5:35 AM, Timothy Macintyre
wrote:
> Does anyone know why I get the error 'too many arguments specified' when
> running the command
> 'dmpstore Setup -s dump1.bin'
>
> Here's a screenshot showing an example
>
> https://dl.dropboxusercontent.com/u/9950356/WP_39.jpg
>
> As
On Nov 6, 2013, at 1:47 PM, Jordan Justen wrote:
> On Wed, Nov 6, 2013 at 10:02 AM, Chris Ruffin wrote:
>> Hi Laszlo, thanks for your feedback. After careful consideration I
>> must agree with you - normally a bus driver would create the child
>> handle and open the parent's protocols by the c
On Wed, Nov 6, 2013 at 10:02 AM, Chris Ruffin wrote:
> Hi Laszlo, thanks for your feedback. After careful consideration I
> must agree with you - normally a bus driver would create the child
> handle and open the parent's protocols by the child controller with
> the BY_CHILD_CONTROLLER attribute.
Hi Laszlo, thanks for your feedback. After careful consideration I
must agree with you - normally a bus driver would create the child
handle and open the parent's protocols by the child controller with
the BY_CHILD_CONTROLLER attribute. Then a device driver would open
the protocol on the child co
resend to the mailing list.
-- Forwarded message --
From:
Date: 2013/11/7
Subject: Re: [edk2] How can NBP get PXE server's IP address?
To: "Fu, Siyuan"
Hi Siyuan-san,
Okay, now I understood how to get the PXE Server's IP clearly by the PXE
Base Code Protocol. Thanks!
Elilo sou
Hi all,
Does anyone know why I get the error 'too many arguments specified' when
running the command 'dmpstore Setup -s dump1.bin'
Here's a screenshot showing an example
https://dl.dropboxusercontent.com/u/9950356/WP_39.jpg
As far as I can tell it matches the input requirementsDMPSTORE [Variab
On 11/06/13 07:04, Jordan Justen wrote:
> On Wed, Oct 30, 2013 at 5:12 PM, Laszlo Ersek wrote:
>> So, I found no regressions in my usual environment (after fixing the
>> ASSERT() with the attached patch).
>
> Does my current ovmf-nvvars branch also fix this issue?
> https://github.com/jljusten/ed
On 11/06/13 06:08, Jordan Justen wrote:
> If the user has set the QEMU_COMMAND environment variable,
> then use it when running QEMU. This can be useful for running
> OVMF with development builds of QEMU.
>
> Contributed-under: TianoCore Contribution Agreement 1.0
> Signed-off-by: Jordan Justen
>
Hi MdeModulePkg.PeiMain maintainer/developers:
I cannot see current Ppi.c->DispatchNotify() uses the passed in parameter
NotifyType for differentiating level of notifications to fire.
Is this one under construction? Or, I missed something in somewhere with this
implemented?
PI 1.3 vol1, page110
23 matches
Mail list logo
