[OASIS Issue Tracker] Updated: (VIRTIO-22) PCI: Allow non-zero revision numbers

From
OASIS Issues Tracker <>
Date
2013-09-23T10:03:52+00:00
ID
1246165493.13881379930679946.JavaMail.tomcat@customer-jira
Thread
[OASIS Issue Tracker] Updated: (VIRTIO-22) PCI: Allow non-zero revision numbers
[ http://tools.oasis-open.org/issues/browse/VIRTIO-22?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Tsirkin updated VIRTIO-22:
----------------------------------

    Proposal: 
https://lists.oasis-open.org/archives/virtio/201309/msg00053.html
-
https://lists.oasis-open.org/archives/virtio/201309/msg00053.html

  was:
https://lists.oasis-open.org/archives/virtio/201309/msg00053.html
-



> PCI: Allow non-zero revision numbers
> ------------------------------------
>
>                 Key: VIRTIO-22
>                 URL: http://tools.oasis-open.org/issues/browse/VIRTIO-22
>             Project: OASIS Virtual I/O Device (VIRTIO) TC
>          Issue Type: Improvement
>            Reporter: Rusty Russell
>            Assignee: Michael Tsirkin
>
> The spec currently says revision number should be 0.  It makes more sense to leave it unspecified, to allow implementations to increment it with software revisions and thus potentially allow workarounds.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://tools.oasis-open.org/issues/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira