OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

virtio-dev message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: [PATCH] pci: remove requirement for revision ID to be 0

While spec previously required revision to be 0 exactly
it turned out not to be an efficient means to
disable legacy drivers - we had to resort to changing
device ID instead.

So let's free up this field making it available for
device makers for hardware versioning.

Resolves VIRTIO-22

Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
 virtio-v1.0-wd01-part1-specification.txt | 8 ++++++--
 1 file changed, 6 insertions(+), 2 deletions(-)

diff --git a/virtio-v1.0-wd01-part1-specification.txt b/virtio-v1.0-wd01-part1-specification.txt
index 62e84f8..d7c00b2 100644
--- a/virtio-v1.0-wd01-part1-specification.txt
+++ b/virtio-v1.0-wd01-part1-specification.txt
@@ -725,14 +725,18 @@ Virtio devices are commonly implemented as PCI devices.
 Any PCI device with Vendor ID 0x1AF4, and Device ID 0x1000 through
-0x103F inclusive is a virtio device[3]. The device must also have a
-Revision ID of 0 to match this specification.
+0x103F inclusive is a virtio device[3].
 The Subsystem Device ID indicates which virtio device is
 supported by the device. The Subsystem Vendor ID should reflect
 the PCI Vendor ID of the environment (it's currently only used
 for informational purposes by the guest).
+ Legacy Interfaces: A Note on PCI Device Discovery
+Transitional devices must also have a Revision ID of 0 to match
+this specification.
+ PCI Device Layout

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]