On 10/16/2013 04:06 PM, Blibbet wrote:
> Thanks to all replies in this thread, useful information!
>
> > Note that Apple's HFS+ EFI driver supplements, but does not
> > replace, the FAT driver. If Apple had replaced the FAT driver with an
> > HFS+ driver, it would have just made it harder to
Thanks to all replies in this thread, useful information!
> Note that Apple's HFS+ EFI driver supplements, but does not
> replace, the FAT driver. If Apple had replaced the FAT driver with an
> HFS+ driver, it would have just made it harder to install other EFI-mode
> OSes on their hardware.
On 10/15/2013 09:23 PM, Blibbet wrote:
>
> It seems silly to require that FAT lives on forever with UEFI, when
> there are more native (and sometimes more secure) solutions for each OS.
> Especialy given UEFI has a file system driver model.
Although some hardware is designed with a single OS in mi
This change implements the VIRTIO_DEVICE_PROTOCOL for the PCI transport
layer.
The VirtIo device drivers will interact with the PCI-based VirtIo devices
through this protocol implementation.
Contributed-under: TianoCore Contribution Agreement 1.0
Signed-off-by: Olivier Martin
---
OvmfPkg/VirtioP
Contributed-under: TianoCore Contribution Agreement 1.0
Signed-off-by: Olivier Martin
---
OvmfPkg/Include/IndustryStandard/Virtio.h |7 +++
1 files changed, 7 insertions(+), 0 deletions(-)
diff --git a/OvmfPkg/Include/IndustryStandard/Virtio.h
b/OvmfPkg/Include/IndustryStandard/Virtio.h
Changelog from v3:
--
- Fixed 'write size' in VIRTIO_DEVICE_WRITE comment
- Made all the functions of the protocol return EFI_STATUS
- Removed 'VIRTIO_GET_GUEST_FEATURES GetGuestFeatures'
- Added a note about the fact VIRTIO_SET_QUEUE_ALIGN is a NOP
- Fixed VIRTIO_GET_DEVICE_STATU
The Device Specific Configuration region is located at different locations
for the VirtIo devices over PCI, PCI with MSI-X capability, MMIO.
Contributed-under: TianoCore Contribution Agreement 1.0
Signed-off-by: Olivier Martin
---
OvmfPkg/Include/IndustryStandard/Virtio.h |7 +++
1 files
These functions did not provide much more than the new protocol functions
VIRTIO_DEVICE_PROTOCOL.ReadDevice() / VIRTIO_DEVICE_PROTOCOL.WriteDevice().
Contributed-under: TianoCore Contribution Agreement 1.0
Signed-off-by: Olivier Martin
---
OvmfPkg/Include/Library/VirtioLib.h | 64 ---
Right now the ARM Platform driver does not do much, but
I expect to move most platform specific code into platform
specific driver in the future.
Contributed-under: TianoCore Contribution Agreement 1.0
Signed-off-by: Olivier Martin
---
.../ArmVExpressPkg/ArmFvpDxe/ArmFvpDxe.c | 49 ++
Why is the virtio-mmio implementation of the protocol a library,
instead of a driver binary?
The UEFI driver model would encourage to create a virtio-mmio driver
instead of a library. But the reasons why I created a library are:
- A virtio-mmio driver would imply an additional protocol that would
This protocol introduces an abstraction to access the VirtIo
Configuration and Device spaces.
The registers in these spaces are located at a different offset and have
a different width whether the transport layer is either PCI or MMIO. This
protocol would also allow to support VirtIo PCI devices wi
Contributed-under: TianoCore Contribution Agreement 1.0
Signed-off-by: Olivier Martin
---
.../ArmVExpressPkg/ArmFvpDxe/ArmFvpDxe.c | 26
.../ArmVExpressPkg/ArmFvpDxe/ArmFvpDxe.inf | 32
.../ArmVExpressPkg/ArmVExpress-RTSM-AEMv8Ax4.dsc
This definition is specific to VirtIo over PCI.
Contributed-under: TianoCore Contribution Agreement 1.0
Signed-off-by: Olivier Martin
---
OvmfPkg/Include/IndustryStandard/Virtio.h | 18 --
1 files changed, 0 insertions(+), 18 deletions(-)
diff --git a/OvmfPkg/Include/IndustryS
Offsets are different between the PCI and MMIO transport layer.
Contributed-under: TianoCore Contribution Agreement 1.0
Signed-off-by: Olivier Martin
---
OvmfPkg/Include/IndustryStandard/Virtio.h | 35 +
1 files changed, 35 insertions(+), 0 deletions(-)
diff --git
Hi,
Not sure whether you notice this email. Just resend in case you miss that.
Thanks,
Ruth
From: Ryan Harkin [mailto:ryan.har...@linaro.org]
Sent: Wednesday, October 16, 2013 6:05 PM
To: Olivier Martin
Cc: edk2-devel@lists.sourceforge.net
Subject: Re: [edk2] [PATCH] MdeModulePkg/ArpDxe: Retrieve
On 9 October 2013 16:31, Ryan Harkin wrote:
> I would like to revive discussion on this patch. It seems it has not been
> accepted, perhaps we could have a comment here from the maintainer about
> what is happening?
>
I think waiting a week is long enough to not make me seem impatient for a
rep
By BlockIO.write() API, you should fill a right value to LBA parameter.
By DiskIO.write() API, you should fill a byte-unit offset to Offset parameter.
Nobody knows which value should be used except for yourself:)
From: parmeshwr_pra...@dell.com [mailto:parmeshwr_pra...@dell.com]
Sent: Wednesday,
17 matches
Mail list logo
