virtualization.lists.linux-foundation.org archive mirror
 help / color / mirror / Atom feed
From: Anthony Liguori <anthony@codemonkey.ws>
To: virtualization@lists.linux-foundation.org
Cc: kernel@vger.kernel.org, Matt Wilson <msw@amazon.com>,
	Anthony Liguori <aliguori@amazon.com>,
	Michael Tsirkin <mst@redhat.com>
Subject: [PATCH] virtio-pci: also bind to Amazon PCI vendor ID
Date: Sun, 14 Sep 2014 20:29:33 -0700	[thread overview]
Message-ID: <1410751773-10519-1-git-send-email-anthony@codemonkey.ws> (raw)

From: Anthony Liguori <aliguori@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 <msw@amazon.com>
Cc: Rusty Russell <rusty@rustcorp.com.au>
Cc: Michael Tsirkin <mst@redhat.com>
Signed-off-by: Anthony Liguori <aliguori@amazon.com>
---
 drivers/virtio/virtio_pci.c |    2 ++
 1 file changed, 2 insertions(+)

diff --git a/drivers/virtio/virtio_pci.c b/drivers/virtio/virtio_pci.c
index 101db3f..9cbac33 100644
--- a/drivers/virtio/virtio_pci.c
+++ b/drivers/virtio/virtio_pci.c
@@ -93,6 +93,8 @@ struct virtio_pci_vq_info
 /* Qumranet donated their vendor ID for devices 0x1000 thru 0x10FF. */
 static DEFINE_PCI_DEVICE_TABLE(virtio_pci_id_table) = {
 	{ PCI_DEVICE(0x1af4, PCI_ANY_ID) },
+	/* Amazon.com vendor ID */
+	{ PCI_DEVICE(0x1d0f, PCI_ANY_ID) },
 	{ 0 }
 };
 
-- 
1.7.9.5

             reply	other threads:[~2014-09-15  3:29 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-15  3:29 Anthony Liguori [this message]
2014-09-15  3:43 ` [PATCH] virtio-pci: also bind to Amazon PCI vendor ID Matt Wilson
2014-09-15  8:20 ` Michael S. Tsirkin
2014-09-15 14:24   ` Anthony Liguori
2014-09-15 16:23     ` Michael S. Tsirkin
2014-09-15 17:58       ` Matt Wilson
2014-09-16  8:54     ` Gerd Hoffmann

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1410751773-10519-1-git-send-email-anthony@codemonkey.ws \
    --to=anthony@codemonkey.ws \
    --cc=aliguori@amazon.com \
    --cc=kernel@vger.kernel.org \
    --cc=mst@redhat.com \
    --cc=msw@amazon.com \
    --cc=virtualization@lists.linux-foundation.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).