Displaying 5 results from an estimated 5 matches for "dn653567".
2014 Sep 15
3
[PATCH] virtio-pci: also bind to Amazon PCI vendor ID
...best as I know, this is not a publicly documented
process.
Do you have any examples of anyone else successfuling WHQL'ing drivers
by just changing the subsystem ID? Microsoft has specific rules about
the usage of the subsystem ID. See
http://msdn.microsoft.com/en-us/library/windows/hardware/dn653567%28v=vs.85%29.aspx.
I don't think it is intended to enable a totally different
implementation of the driver based on subsystem ID.
Certainly, this is not expected with typical PCI devices.
> On the host side, you will need a QEMU patch to allow libvirt control of
> the subsystem vendor I...
2014 Sep 15
3
[PATCH] virtio-pci: also bind to Amazon PCI vendor ID
...best as I know, this is not a publicly documented
process.
Do you have any examples of anyone else successfuling WHQL'ing drivers
by just changing the subsystem ID? Microsoft has specific rules about
the usage of the subsystem ID. See
http://msdn.microsoft.com/en-us/library/windows/hardware/dn653567%28v=vs.85%29.aspx.
I don't think it is intended to enable a totally different
implementation of the driver based on subsystem ID.
Certainly, this is not expected with typical PCI devices.
> On the host side, you will need a QEMU patch to allow libvirt control of
> the subsystem vendor I...
2014 Sep 15
0
[PATCH] virtio-pci: also bind to Amazon PCI vendor ID
...device, a new
initial device submission must be made (with full testing).
All reseller submissions are subject to audit.
Seems to say you can do this.
> Microsoft has specific rules about
> the usage of the subsystem ID. See
> http://msdn.microsoft.com/en-us/library/windows/hardware/dn653567%28v=vs.85%29.aspx.
> I don't think it is intended to enable a totally different
> implementation of the driver based on subsystem ID.
> Certainly, this is not expected with typical PCI devices.
Why not? Changing device ID doesn't seem to be very different.
It's not uncommon fo...
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