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


Help: OASIS Mailing Lists Help | MarkMail Help

virtio-comment message

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

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

OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> writes:
> Rusty Russell created VIRTIO-102:
> ------------------------------------
>              Summary: 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
>             Reporter: Rusty Russell
>             Assignee: Michael Tsirkin
> 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.

Confused.  We don't use device IDs except to restrict their range (that
was because Qumranet only granted us those IDs; we could ask RH to
expand them).

        Vendor ID = 0x1AF4
        Device ID = 0x1000 - 0x103F
        Subsystem vendor ID = <your ID here>
        Subsystem ID = <VIRTIO TYPE>

I don't understand your proposal?


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