There is a DEBUG warning printout in VirtioMmioDeviceLib if the current
device's VendorID does not match the traditional 16-bit Red Hat PCIe
vendor ID used with virtio-pci. The virtio-mmio vendor ID is 32-bit and
has no connection to the PCIe registry.
Most specifically, this causes a bunch of noise when booting an AArch64
QEMU platform, since QEMU's virtio-mmio implementation used 'QEMU' as
the vendor ID:
VirtioMmioInit: Warning:
The VendorId (0x554D4551) does not match the VirtIo VendorId (0x1AF4).
Drop the warning message.
Cc: Jordan Justen <jordan.l.justen@intel.com>
Cc: Laszlo Ersek <lersek@redhat.com>
Cc: Ard Biesheuvel <ard.biesheuvel@arm.com>
Signed-off-by: Leif Lindholm <leif@nuviainc.com>
Reviewed-by: Laszlo Ersek <lersek@redhat.com>
Reviewed-by: Philippe Mathieu-Daudé <philmd@redhat.com>
)\r
{\r
UINT32 MagicValue;\r
- UINT32 VendorId;\r
UINT32 Version;\r
\r
//\r
return EFI_UNSUPPORTED;\r
}\r
\r
- //\r
- // Double-check MMIO-specific values\r
- //\r
- VendorId = VIRTIO_CFG_READ (Device, VIRTIO_MMIO_OFFSET_VENDOR_ID);\r
- if (VendorId != VIRTIO_VENDOR_ID) {\r
- //\r
- // The ARM Base and Foundation Models do not report a valid VirtIo VendorId.\r
- // They return a value of 0x0 for the VendorId.\r
- //\r
- DEBUG((DEBUG_WARN, "VirtioMmioInit: Warning: The VendorId (0x%X) does not "\r
- "match the VirtIo VendorId (0x%X).\n",\r
- VendorId, VIRTIO_VENDOR_ID));\r
- }\r
-\r
return EFI_SUCCESS;\r
}\r
\r