Eric,
In ExtractConfig function of HII config access protocol, I am required to
return a
This header includes the following 3 fields:
::= 'GUID='
::= 'NAME='
::= 'PATH='
Assuming I do not use a Var Store, but decide to save data locally -
How should I fill the GUID and Name fields?
Thanks,
On Wed, Nov 13, 2013 at 08:03:39AM +0100, Gerd Hoffmann wrote:
> Hi,
>
> > > The first thing that comes in mind is to reuse E820 table for memory map
> > > plus some extra fields for io / mmio resources. But I guess UEFI is the
> > > new world so stuffs like E820 from old world will be less popu
On Tue, Nov 12, 2013 at 11:51:10AM -0800, Jordan Justen wrote:
> On Tue, Nov 12, 2013 at 10:33 AM, Wei Liu wrote:
> > Hi all
> >
> > Currently OVMF determines memory size by consulting CMOS, then it makes
> > up memory map of its own.
> >
> > Consulting memory size by reading CMOS limits the RAM s
On Mi, 2013-11-13 at 11:58 +, Wei Liu wrote:
> On Wed, Nov 13, 2013 at 08:03:39AM +0100, Gerd Hoffmann wrote:
> > Hi,
> >
> > > > The first thing that comes in mind is to reuse E820 table for memory map
> > > > plus some extra fields for io / mmio resources. But I guess UEFI is the
> > > > n
On Wed, Nov 13, 2013 at 02:53:34PM +0100, Gerd Hoffmann wrote:
> On Mi, 2013-11-13 at 11:58 +, Wei Liu wrote:
> > On Wed, Nov 13, 2013 at 08:03:39AM +0100, Gerd Hoffmann wrote:
> > > Hi,
> > >
> > > > > The first thing that comes in mind is to reuse E820 table for memory
> > > > > map
> > >
Ben -
When you say "I do not use a Var Store" what do you mean? Why not use a
NAME_VALUE var store, instead of the traditional buffer var store? The Name
Value does not even assume that it is a bucket of bytes (thus, no offsets).
Actually, the Form Browser does not (for the most part) save anyt
Hi,
> > > MMIO holes, IO range created by hvmloader.
> >
> > Why? All (memory) address space not backed by ram effectively is mmio.
> > There is no need to explicitly declare holes ...
> >
>
> Yes there is, because hvmloader is in charge of declaring holes.
Why does it declare holes in the
Hi,
On Nov 12, 2013, at 7:43 PM, "Tian, Feng" wrote:
>> From h/w view, SCSI CD_ROM could support r/w media, Just like SATA CD_ROM.
>> right?
> So treating all SCSI CD_ROM to read only is proper here? Shall we write the
> media first, if fail, then get sense data to judge if write protected?
Tim,
I mean I do not use EFI Var Store. I am however using Buffer Var Store as my
VFR storage.
Also, I do not use an EFI variable locally to save the data.
So I wasn't sure what GUID it was expecting in the , since I don't
have a GUID from neither EFI Var Store, nor from local EFI variables.
Th
On Wed, Nov 13, 2013 at 03:23:05PM +0100, Gerd Hoffmann wrote:
> Hi,
>
> > > > MMIO holes, IO range created by hvmloader.
> > >
> > > Why? All (memory) address space not backed by ram effectively is mmio.
> > > There is no need to explicitly declare holes ...
> > >
> >
> > Yes there is, beca
Hi, Tycho
The IdeBusDxe in IntelFrameworkModulePkg is obsoleted and is replaced by AtaBus
and ScsiBus.
For your question, I would suggest updating code like below:
ScsiDiskDetectMedia():
1) send Test_Unit_Ready cmd
2) send Get_Configuration cmd <- get medium profile info here.
3) send READ_CAPA
Ben,
For your situation, I think varstore is good for you.
For the varstore definition, you can see the DriverSample code in
MdeModulePkg/Universal/DriverSampleDxe. For how to maintain varstore storage,
browser will call ExtractConfig/RouteConfig function provide by your driver to
get /set valu
12 matches
Mail list logo
