qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Anthony Liguori <anthony@codemonkey.ws>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [6076] This should have been added in Gerd's previous commit.
Date: Wed, 17 Dec 2008 21:32:38 +0000	[thread overview]
Message-ID: <E1LD40T-0005MV-W1@cvs.savannah.gnu.org> (raw)

Revision: 6076
          http://svn.sv.gnu.org/viewvc/?view=rev&root=qemu&revision=6076
Author:   aliguori
Date:     2008-12-17 21:32:37 +0000 (Wed, 17 Dec 2008)

Log Message:
-----------
This should have been added in Gerd's previous commit.

Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>

Added Paths:
-----------
    trunk/pci-ids.txt

Added: trunk/pci-ids.txt
===================================================================
--- trunk/pci-ids.txt	                        (rev 0)
+++ trunk/pci-ids.txt	2008-12-17 21:32:37 UTC (rev 6076)
@@ -0,0 +1,30 @@
+
+PCI IDs for qemu
+================
+
+Red Hat, Inc. donates a part of its device ID range to qemu, to be used for
+virtual devices.  The vendor ID is 1af4 (formerly Qumranet ID).
+
+The 1000 -> 10ff device ID range is used for VirtIO devices.
+
+The 1100 device ID is used as PCI Subsystem ID for existing hardware
+devices emulated by qemu.
+
+All other device IDs are reserved.
+
+
+VirtIO Device IDs
+-----------------
+
+1af4:1000  network device
+1af4:1001  block device
+1af4:1002  balloon device
+
+1af4:1003  Reserved.
+   to      Contact Gerd Hoffmann <kraxel@redhat.com> to get a
+1af4:10ef  device ID assigned for your new virtio device.
+
+1af4:10f0  Available for experimental usage without registration.  Must get
+   to      official ID when the code leaves the test lab (i.e. when seeking
+1af4:10ff  upstream merge or shipping a distro/product) to avoid conflicts.
+

                 reply	other threads:[~2008-12-17 21:32 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=E1LD40T-0005MV-W1@cvs.savannah.gnu.org \
    --to=anthony@codemonkey.ws \
    --cc=qemu-devel@nongnu.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).