Liming,
Thanks for your explanation!
I understood the way Notify PPIs been handled by current design even thought
the NotifyType is not referenced in DispatchNotify().
|-> InstallPpi
NotifyPpi <-|
+-+-
Hi everyone
I'd like to ask you, if someone know a way to work with the sound card at
UEFI environment. I mean. how to play a simple sound using the sound card
at a UEFI application.
As far as I could research, to do this I'll need to develop a driver for
the device.
Am I going on the right way o
On 11/06/13 23:29, Jordan Justen wrote:
> 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
On 11/06/13 23:29, Jordan Justen wrote:
> 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 213d86
On 11/06/13 23:29, Jordan Justen wrote:
> 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
On 11/06/13 23:30, Jordan Justen wrote:
> If QEMU flash is detected, this module will install
> FirmwareVolumeBlock support for the QEMU flash device.
>
> It will also set PCDs with the results that:
> 1. OvmfPkg/EmuVariableFvbRuntimeDxe will be disabled
> 2. MdeModulePkg variable services will re
Hi,
First Question:
The examples I have seen for HII Config Access Protocol have used an EFI
Variable to store the data and retrieve it.
Is it possible to just use a defined structure and set/get the values from it.
It doesn't seem that GetVariable/SetVariable are necessary if I can just save
t
On Nov 7, 2013, at 4:01 AM, Rafael Machado
wrote:
> Hi everyone
>
> I'd like to ask you, if someone know a way to work with the sound card at
> UEFI environment. I mean. how to play a simple sound using the sound card at
> a UEFI application.
>
> As far as I could research, to do this I'll
Let me clarify my third question:
The example shows code that when receiving a NULL request
string in ExtractConfig, will build a .
This will be used to construct a response string that
holds the fields and data of this VFR Form, needed by ExtractConfig().
I would like to continue to support t
Thank you Andrew!
2013/11/7 Andrew Fish
>
> On Nov 7, 2013, at 4:01 AM, Rafael Machado <
> rafaelrodrigues.mach...@gmail.com> wrote:
>
> > Hi everyone
> >
> > I'd like to ask you, if someone know a way to work with the sound card
> at UEFI environment. I mean. how to play a simple sound using t
On 11/06/13 23:29, Jordan Justen wrote:
> 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 w
On Nov 6, 2013, at 11:41 PM, Andrew Fish wrote:
>
> 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 ch
On 11/07/13 17:28, Laszlo Ersek wrote:
> On 11/06/13 23:29, Jordan Justen wrote:
>> 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 attempt
On Thu, Nov 7, 2013 at 10:07 AM, Laszlo Ersek wrote:
> On 11/07/13 17:28, Laszlo Ersek wrote:
>> On 11/06/13 23:29, Jordan Justen wrote:
>>> https://github.com/jljusten/edk2.git ovmf-nvvars-v2
>>>
>>> This series implements support for QEMU's emulated
>>> system flash.
>>>
>>> This allows for pers
On 11/07/13 21:34, Jordan Justen wrote:
> On Thu, Nov 7, 2013 at 10:07 AM, Laszlo Ersek wrote:
>> I.
>> This is a QEMU regression (somewhere between v1.6.0 and v1.7.0-rc0),
>> I'll have to bisect it.
>
> I bisected this to QEMU a53ae8e9, and I CC'd you on the email about it
> that I sent to qemu
This is a QEMU bug report, only disguised as an edk2-devel followup.
The problem in a nutshell is that the OVMF binary, placed into pflash
(read-only KVM memslot) used to run in qemu-1.6, but it fails to start
in qemu-1.7. The OVMF reset vector reads as 0xFF bytes.
(Jordan and myself started writ
Il 07/11/2013 22:12, Laszlo Ersek ha scritto:
> -7ffe (prio 0, RW): system
> [...]
> 6000- (prio 0, RW): alias pci-hole @pci
> 6000-
> [...]
> ffe0- (prio 0, R-): system.flash
>
On 11/07/13 22:21, Paolo Bonzini wrote:
> Il 07/11/2013 22:12, Laszlo Ersek ha scritto:
>> -7ffe (prio 0, RW): system
>> [...]
>> 6000- (prio 0, RW): alias pci-hole @pci
>> 6000-
>> [...]
>> ffe
Il 07/11/2013 22:24, Marcel Apfelbaum ha scritto:
> Thank you Laszlo for the detailed info!
> I think the problem is right above. Why pci-hole and system.flash collide?
> IMHO we should not play with priorities here, better solve the collision.
We need to audit all the other boards that support PC
On 11/07/13 22:24, Marcel Apfelbaum wrote:
> On Thu, 2013-11-07 at 22:12 +0100, Laszlo Ersek wrote:
>> adding subregion 'pci-hole' to region 'system' at offset 6000
>> warning: subregion collision 6000/a000 (pci-hole) vs
>> ffe0/20 (system.flash)
> Thank you Laszlo for the
On 11/07/13 22:24, Marcel Apfelbaum wrote:
> Why pci-hole and system.flash collide? IMHO we should not play with
> priorities here, better solve the collision.
What about this "beautiful" series? It produces
memory
-000f (prio 0, RW): system
[...]
6000
... upwards through the following call chain:
pc_init1() | pc_q35_init()
pc_memory_init()
pc_system_firmware_init()
pc_system_flash_init()
Signed-off-by: Laszlo Ersek
---
include/hw/i386/pc.h | 6 --
hw/i386/pc.c | 5 +++--
hw/i386/pc_piix.c| 3 ++-
hw/i38
Signed-off-by: Laszlo Ersek
---
hw/i386/pc_piix.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/hw/i386/pc_piix.c b/hw/i386/pc_piix.c
index 6e2c027..9bda20a 100644
--- a/hw/i386/pc_piix.c
+++ b/hw/i386/pc_piix.c
@@ -152,7 +152,7 @@ static void pc_init1(QEMUMachineInitArgs *a
Ben,
Add my comments below.
Thanks,
Eric
From: Ben Schroeder [mailto:ben...@mellanox.com]
Sent: Thursday, November 07, 2013 11:53 PM
To: edk2-devel@lists.sourceforge.net
Subject: Re: [edk2] Hii and EFI Variables
Let me clarify my third question:
The example shows code that when receiving a NULL
On Thu, Nov 7, 2013 at 2:23 PM, Laszlo Ersek wrote:
> ... upwards through the following call chain:
>
> pc_init1() | pc_q35_init()
> pc_memory_init()
> pc_system_firmware_init()
> pc_system_flash_init()
>
> Signed-off-by: Laszlo Ersek
> ---
> include/hw/i386/pc.h | 6 --
Andrew:
Rule file has two styles. ?.c, or *.obj. ? is for single file, * is for all
files.
For your case, what's your output? Z.bin? If so, you can add rule for ?.xyz
to create .xyz2, then add rule for *.xyz2 to $(BASE_NAME).bin
Thanks
Liming
From: Andrew Fish [mailto:af...@apple.com]
Sent:
26 matches
Mail list logo
