Ovmf/Xen: move XenBusDxe to abstract XENIO_PROTOCOL
While Xen on Intel uses a virtual PCI device to communicate the base address of the grant table, the ARM implementation uses a DT node, which is fundamentally incompatible with the way XenBusDxe is implemented, i.e., as a UEFI Driver Model implementation for a PCI device. Contributed-under: TianoCore Contribution Agreement 1.0 Acked-by: Laszlo Ersek <lersek@redhat.com> Reviewed-by: Anthony PERARD <anthony.perard@citrix.com> Signed-off-by: Ard Biesheuvel <ard.biesheuvel@linaro.org> Signed-off-by: Laszlo Ersek <lersek@redhat.com> git-svn-id: https://svn.code.sf.net/p/edk2/code/trunk/edk2@16973 6f19259b-4bc3-4df7-8a09-765794883524
This commit is contained in:
@@ -138,7 +138,7 @@ XenBusAddDevice (
|
||||
XENBUS_PRIVATE_DATA *Private;
|
||||
EFI_STATUS Status;
|
||||
XENBUS_DEVICE_PATH *TempXenBusPath;
|
||||
VOID *ChildPciIo;
|
||||
VOID *ChildXenIo;
|
||||
|
||||
AsciiSPrint (DevicePath, sizeof (DevicePath),
|
||||
"device/%a/%a", Type, Id);
|
||||
@@ -208,8 +208,8 @@ XenBusAddDevice (
|
||||
}
|
||||
|
||||
Status = gBS->OpenProtocol (Dev->ControllerHandle,
|
||||
&gEfiPciIoProtocolGuid,
|
||||
&ChildPciIo, Dev->This->DriverBindingHandle,
|
||||
&gXenIoProtocolGuid,
|
||||
&ChildXenIo, Dev->This->DriverBindingHandle,
|
||||
Private->Handle,
|
||||
EFI_OPEN_PROTOCOL_BY_CHILD_CONTROLLER);
|
||||
if (EFI_ERROR (Status)) {
|
||||
|
Reference in New Issue
Block a user