Displaying 6 results from an estimated 6 matches for "4cc9".
Did you mean:
4ac9
2014 Sep 15
3
[PATCH] virtio-pci: also bind to Amazon PCI vendor ID
From: Anthony Liguori <aliguori at amazon.com>
See https://issues.oasis-open.org/browse/VIRTIO-16 although it
was prematurely closed.
Red Hat has non-redistributable Windows drivers and Microsoft
will not allow anyone else to WHQL certify drivers using that
vendor ID. That makes it impossible to use virtio drivers with
a Windows guest without changing the vendor ID.
Cc: Matt Wilson
2014 Sep 15
3
[PATCH] virtio-pci: also bind to Amazon PCI vendor ID
From: Anthony Liguori <aliguori at amazon.com>
See https://issues.oasis-open.org/browse/VIRTIO-16 although it
was prematurely closed.
Red Hat has non-redistributable Windows drivers and Microsoft
will not allow anyone else to WHQL certify drivers using that
vendor ID. That makes it impossible to use virtio drivers with
a Windows guest without changing the vendor ID.
Cc: Matt Wilson
2014 Sep 15
0
[PATCH] virtio-pci: also bind to Amazon PCI vendor ID
...o WHQL.
On the host side, you will need a QEMU patch to allow libvirt control of
the subsystem vendor ID.
All this while all Linux guests will keep working without changes,
which seems like a better approach.
Looking on the web, I found:
http://download.microsoft.com/download/1/6/1/161ba512-40e2-4cc9-843a-923143f3456c/pciidspec-11.doc
"Test will read and properly concatenate PCI IDs and verify uniqueness"
this is likely what you are running into: IDs must be unique,
so if you want to put your driver in Microsoft's database,
it must match a different set of IDs.
But you should not...
2014 Sep 15
3
[PATCH] virtio-pci: also bind to Amazon PCI vendor ID
...ll need a QEMU patch to allow libvirt control of
> the subsystem vendor ID.
>
> All this while all Linux guests will keep working without changes,
> which seems like a better approach.
>
> Looking on the web, I found:
> http://download.microsoft.com/download/1/6/1/161ba512-40e2-4cc9-843a-923143f3456c/pciidspec-11.doc
> "Test will read and properly concatenate PCI IDs and verify uniqueness"
> this is likely what you are running into: IDs must be unique,
> so if you want to put your driver in Microsoft's database,
> it must match a different set of IDs....
2014 Sep 15
3
[PATCH] virtio-pci: also bind to Amazon PCI vendor ID
...ll need a QEMU patch to allow libvirt control of
> the subsystem vendor ID.
>
> All this while all Linux guests will keep working without changes,
> which seems like a better approach.
>
> Looking on the web, I found:
> http://download.microsoft.com/download/1/6/1/161ba512-40e2-4cc9-843a-923143f3456c/pciidspec-11.doc
> "Test will read and properly concatenate PCI IDs and verify uniqueness"
> this is likely what you are running into: IDs must be unique,
> so if you want to put your driver in Microsoft's database,
> it must match a different set of IDs....
2014 Sep 15
0
[PATCH] virtio-pci: also bind to Amazon PCI vendor ID
...rt control of
> > the subsystem vendor ID.
> >
> > All this while all Linux guests will keep working without changes,
> > which seems like a better approach.
> >
> > Looking on the web, I found:
> > http://download.microsoft.com/download/1/6/1/161ba512-40e2-4cc9-843a-923143f3456c/pciidspec-11.doc
> > "Test will read and properly concatenate PCI IDs and verify uniqueness"
> > this is likely what you are running into: IDs must be unique,
> > so if you want to put your driver in Microsoft's database,
> > it must match a d...