I want to store a question value into a 'volatile' storage variable, because
the value is temporal and does not need to be saved at all. According to UEFI
Driver Writer's Guide, question values are always saved in non-volatile storage
(it can be Buffer Storage, Name/Value storage or EFI variable
If there are no other concerns, can someone commit this to SVN please?
Thanks,
--Samer
From: El-Haj-Mahmoud, Samer
Sent: Monday, September 30, 2013 10:56 AM
To: edk2-devel@lists.sourceforge.net
Subject: Re: [edk2] Patch: Fix misc DEBUG_ERROR messages
Attached updated patch with these changes.
On Oct 2, 2013, at 2:03 AM, Wei Liu wrote:
> On Tue, Oct 01, 2013 at 10:33:49AM -0700, Andrew Fish wrote:
>>
>> On Oct 1, 2013, at 10:10 AM, Wei Liu wrote:
>>
>>> Hi OVMF experts
>>>
>>> I'm trying to make OVMF work with Xen HVM and discover a possible bug in
>>> EDK2 OVMF. The root cause is
On Oct 2, 2013, at 6:40 AM, ASM wrote:
> On 1 October 2013 18:47, Andrew Fish wrote:
>> The EFI Driver Model, EFI_DRIVER_BINDING_PROTOCOL, assumes that an
>> EFI_HANDLE exists that you can connect to. So the Handle that represents the
>> 1st device path node is usually added by a DXE driver.
On 1 October 2013 18:47, Andrew Fish wrote:
> The EFI Driver Model, EFI_DRIVER_BINDING_PROTOCOL, assumes that an EFI_HANDLE
> exists that you can connect to. So the Handle that represents the 1st device
> path node is usually added by a DXE driver. So on most platform this is
> usually the PCI
On Tue, Oct 01, 2013 at 10:33:49AM -0700, Andrew Fish wrote:
>
> On Oct 1, 2013, at 10:10 AM, Wei Liu wrote:
>
> > Hi OVMF experts
> >
> > I'm trying to make OVMF work with Xen HVM and discover a possible bug in
> > EDK2 OVMF. The root cause is that EmuVariableFvbRuntimeDxe sets FTW
> > spare s
