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

 


Help: OASIS Mailing Lists Help | MarkMail Help

virtio message

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


Subject: [OASIS Issue Tracker] (VIRTIO-102) PCI Discovery


     [ https://tools.oasis-open.org/issues/browse/VIRTIO-102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Tsirkin updated VIRTIO-102:
-----------------------------------

    Environment: Andrew Thornton <andrewth@google.com>  (was: Andrew Thornton <andrewth@google.com>)
       Proposal: 1401739703-5442-1-git-send-email-mst@redhat.com">http://mid.gmane.org/1401739703-5442-1-git-send-email-mst@redhat.com  (was: http://mid.gmane.org/1401569411-17718-1-git-send-email-mst@redhat.com)

> PCI Discovery
> -------------
>
>                 Key: VIRTIO-102
>                 URL: https://tools.oasis-open.org/issues/browse/VIRTIO-102
>             Project: OASIS Virtual I/O Device (VIRTIO) TC
>          Issue Type: Sub-task
>    Affects Versions: virtio 1.0 csprd01
>         Environment: Andrew Thornton <andrewth@google.com>
>            Reporter: Rusty Russell
>
> 4.1.1 PCI Device Discovery
> This use of PCI device ID’s is an unusual way to handle PCI identification and plays badly with Windows.  Could we instead require the device ID be 0x10xx where xx is the already defined sub-vendor code.  This reflects the current reality of implementation requirements.



--
This message was sent by Atlassian JIRA
(v6.2.2#6258)


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