intel.com]
> *Sent:* Sunday, November 02, 2014 7:09 PM
> *To:* edk2-devel@lists.sourceforge.net
> *Subject:* Re: [edk2] Non-Volatile Variable Storage
>
> Hi, Alok
>
> IMHO, One possible way to solve OS and F/W interaction for controlling
> same h/w controller is to implem
2014 5:19 AM
To: edk2-devel@lists.sourceforge.net
Subject: Re: [edk2] Non-Volatile Variable Storage
>> which you can stop the h/w DMA, save OS context, do your task and then
>> restore OS context
Hi Feng,
Thanks. Yes this is one possibly but the implementation is always
is universal for such storage and we all are
coming up on our own solution
Thanks
-Alok
From: Tian, Feng [mailto:feng.t...@intel.com]
Sent: Sunday, November 02, 2014 7:09 PM
To: edk2-devel@lists.sourceforge.net
Subject: Re: [edk2] Non-Volatile Variable Storage
Hi, Alok
IMHO, One possible way
, then the content may be corrupted.
Thanks
Feng
From: Zimmer, Vincent [mailto:vincent.zim...@intel.com]
Sent: Saturday, November 01, 2014 05:07
To: edk2-devel@lists.sourceforge.net
Subject: Re: [edk2] Non-Volatile Variable Storage
Good points on both sides.
I see UEFI Forum w/ USWG and ASWG (UEFI
t; >DXE phase requires it. So, you can implement FVB protocol to
>> handle
>> >> > the
>> >> >write operation in the cached memory and storage.
>> >>
>> >> Well, we worked around this pretty nicely in OVMF when we wanted to
>
FVB write
> >> hook to signal that the variables need to be serialized to the FAT FS.
> >>
> >> I'm disappointed that I was not able to make this system replace
> >> MdeModulePkg/Universal/Variable/EmuRuntimeDxe and DuetPkg/FSVariable
> >> because
kg/Universal/Variable/EmuRuntimeDxe and DuetPkg/FSVariable
>> because then we could always just use the single variable driver:
>> MdeModulePkg/Universal/Variable/RuntimeDxe
>>
>> Now that QEMU/KVM has real flash support, I suppose that some parts of
>>
> On Oct 31, 2014, at 5:00 PM, Narinder Dhillon wrote:
>
> Hi Jordan,
>
> What is the difference between RuntimeDxe, EmuRuntimeDxe ?
> From looking at the code, seems like RuntimeDxe is more complete
> implementation. But when I switch to that, I get errors from DxeMain.
> Not sure why.
> Than
e/RuntimeDxe
>
> Now that QEMU/KVM has real flash support, I suppose that some parts of
> this code now has an expiration date in OVMF... (The desire to
> actually serialize the variables to/from disk is greatly diminished.)
>
> -Jordan
>
> >From: Narinder Dhillon [ma
>Sent: Friday, October 31, 2014 12:12 PM
>To: edk2-devel@lists.sourceforge.net
>Subject: [edk2] Non-Volatile Variable Storage
>
>
>
>Hi All,
>
>
>
>I am attempting to implement a non-volatile variable storage in an eMMC
>dev
lt;mailto:edk2-devel@lists.sourceforge.net>
> Subject: Re: [edk2] Non-Volatile Variable Storage
>
> Good points on both sides.
> I see UEFI Forum w/ USWG and ASWG (UEFI and ACPI spec, resp) as a place to
> explore this a little further, although Fish may be right about ultimat
you add the UEFI Secure Boot in the
equation...
From: Zimmer, Vincent [mailto:vincent.zim...@intel.com]
Sent: 31 October 2014 21:07
To: edk2-devel@lists.sourceforge.net
Subject: Re: [edk2] Non-Volatile Variable Storage
Good points on both sides.
I see UEFI Forum w/ USWG and ASWG (UEFI
.
Vincent
From: Pant, Alok [mailto:alok.p...@amd.com]
Sent: Friday, October 31, 2014 1:56 PM
To: edk2-devel@lists.sourceforge.net
Subject: Re: [edk2] Non-Volatile Variable Storage
Hi Andrew. Thanks. Yes, I understand and agree with your point. All I point is
there is no universally-agreed
ion, or each come up with their
own unique implementation
Thanks again
-Alok
From: Andrew Fish [mailto:af...@apple.com]
Sent: Friday, October 31, 2014 12:24 PM
To: edk2-devel@lists.sourceforge.net
Subject: Re: [edk2] Non-Volatile Variable Storage
On Oct 31, 2014, at 7:58 AM, Pant, Alok
m
he driver
> (and maybe the OS) and firmware. The UEFI spec avoids discussing OS
> specifics, and trying to recommend hardware implementations (as hardware
> changes at a rapid rate).
>
> Thanks,
>
> Andrew Fish
>
>> From: Olivier Martin [mailto:olivier.mar...@arm.com
>
;
> *From:* Olivier Martin [mailto:olivier.mar...@arm.com
> ]
> *Sent:* Friday, October 31, 2014 9:04 AM
> *To:* edk2-devel@lists.sourceforge.net
> *Subject:* Re: [edk2] Non-Volatile Variable Storage
>
> Something you have to be aware about Non-Volatile UEFI variables is they
> might need
04 AM
> To: edk2-devel@lists.sourceforge.net <mailto:edk2-devel@lists.sourceforge.net>
> Subject: Re: [edk2] Non-Volatile Variable Storage
>
> Something you have to be aware about Non-Volatile UEFI variables is they
> might need to be accessible when the OS is running (th
Martin [mailto:olivier.mar...@arm.com]
Sent: Friday, October 31, 2014 9:04 AM
To: edk2-devel@lists.sourceforge.net
Subject: Re: [edk2] Non-Volatile Variable Storage
Something you have to be aware about Non-Volatile UEFI variables is they might
need to be accessible when the OS is running (throug
between the OS
kernel and the UEFI firmware.
From: Narinder Dhillon [mailto:ndhillo...@gmail.com]
Sent: 31 October 2014 04:12
To: edk2-devel@lists.sourceforge.net
Subject: [edk2] Non-Volatile Variable Storage
Hi All,
I am attempting to implement a non-volatile variable storage in an
: [edk2] Non-Volatile Variable Storage
Hi All,
I am attempting to implement a non-volatile variable storage in an eMMC device.
After about a week of looking around, I have come to the realization that there
is no such feature in edk2.
Is this correct ?
Looking at 'variable' drivers
Hi All,
I am attempting to implement a non-volatile variable storage in an eMMC
device. After about a week of looking around, I have come to the
realization that there is no such feature in edk2.
Is this correct ?
Looking at 'variable' drivers, it seems that the variable storage for both
volatile
21 matches
Mail list logo
