Suppose a name/value storage has been defined in VFR file like below:
//
// Define a name/value storage (EFI_IFR_VARSTORE_NAME_VALUE)
//
namevaluevarstore NameValueVar1,
name = STRING_TOKEN(STR_VALUE1),
name = STRING_TOKEN(STR_VALUE2),
guid = ABC_FORMSET_GUID;
Now to create
Hi Mark,
just my 2 cents:
On 09/26/13 21:33, Mark Salter wrote:
> I've been trying out this patch series on AArch64 foundation model.
> I have UEFI booting a linux kernel image in an EFI system partition.
> But the kernel itself doesn't see the virtio device. If I boot with
> an UEFI image withou
I've been trying out this patch series on AArch64 foundation model.
I have UEFI booting a linux kernel image in an EFI system partition.
But the kernel itself doesn't see the virtio device. If I boot with
an UEFI image without virtio support built in, the same kernel does
see the virtio disk device
On 09/26/13 20:49, Laszlo Ersek wrote:
>> > +
>> > +**/
>> > +STATIC
>> > +EFI_STATUS
>> > +EFIAPI
>> > +VirtioMmioInit (
>> > + IN OUT VIRTIO_MMIO_DEVICE *Device
>> > + )
>> > +{
>> > + // Set Mmio Page Size
>> > +
>> > + UINT8 NextDevStat;
>> > + UINT32 MagicValue;
>> > + UINT32
On 09/23/13 15:37, Olivier Martin wrote:
> Contributed-under: TianoCore Contribution Agreement 1.0
> Signed-off-by: Olivier Martin
> ---
> OvmfPkg/Include/Library/VirtioMmioDeviceLib.h | 48
> .../Library/VirtioMmioDeviceLib/VirtioMmioDevice.c | 201 +
> .../Library/Virti
On 09/25/13 19:16, Laszlo Ersek wrote:
> On 09/23/13 15:37, Olivier Martin wrote:
>> diff --git a/OvmfPkg/VirtioPciDeviceDxe/VirtioPciFunctions.c
>> b/OvmfPkg/VirtioPciDeviceDxe/VirtioPciFunctions.c
>> new file mode 100644
>> index 000..15c4348
>> --- /dev/null
>> +++ b/OvmfPkg/VirtioPciDevic
