diff options
author | mstsirkin <mstsirkin@0c8fb4dd-22a2-4bb5-bc14-6c75a5f43652> | 2013-09-30 06:09:46 +0000 |
---|---|---|
committer | mstsirkin <mstsirkin@0c8fb4dd-22a2-4bb5-bc14-6c75a5f43652> | 2013-09-30 06:09:46 +0000 |
commit | 2c758494de010bf29db35716c13f45263fd07ed1 (patch) | |
tree | 095204286fad26bc119132159cd997e52bf3275f | |
parent | f9548545a3ec6ce0cf85adbd7fbb4eeab9d23348 (diff) |
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
Approved OASIS meeting 2013-09-24.
Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
git-svn-id: https://tools.oasis-open.org/version-control/svn/virtio@48 0c8fb4dd-22a2-4bb5-bc14-6c75a5f43652
-rw-r--r-- | virtio-v1.0-wd01-part1-specification.txt | 8 |
1 files changed, 6 insertions, 2 deletions
diff --git a/virtio-v1.0-wd01-part1-specification.txt b/virtio-v1.0-wd01-part1-specification.txt index d65e8f2..1c2214f 100644 --- a/virtio-v1.0-wd01-part1-specification.txt +++ b/virtio-v1.0-wd01-part1-specification.txt @@ -682,14 +682,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). +2.3.1.1.1 Legacy Interfaces: A Note on PCI Device Discovery +------------------------- +Transitional devices must also have a Revision ID of 0 to match +this specification. + 2.3.1.2. PCI Device Layout ------------------------- |