Uploaded image for project: 'OASIS Virtual I/O Device (VIRTIO) TC'
  1. OASIS Virtual I/O Device (VIRTIO) TC
  2. VIRTIO-16

Allow anyone to whql their windows drivers

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: virtio 1.0 csprd02
    • Fix Version/s: virtio 1.0 csprd03
    • Labels:
      None
    • Resolution:
      Hide

      I think anyone can use a different subsystem vendor id and whql the driver. virtio-102 will make this even easier, by making the subsystem id flexible. Let's close this and re-open if someone tries to do this and runs into a problem.

      Closed as per minutes 2014-06-04: https://lists.oasis-open.org/archives/virtio/201406/msg00013.html

      Show
      I think anyone can use a different subsystem vendor id and whql the driver. virtio-102 will make this even easier, by making the subsystem id flexible. Let's close this and re-open if someone tries to do this and runs into a problem. Closed as per minutes 2014-06-04: https://lists.oasis-open.org/archives/virtio/201406/msg00013.html

      Description

      RedHat (nee Quamranet) kindly donated the PCI ID we use for virtio in the draft. Apparently Microsoft will only allow them (as ID owners) to have their windows drivers certified. If possible, we would like to find a way that any implementor can have their drivers certified.

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              rusty Rusty Russell (Inactive)
            • Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: