From: Christian Pinto <c.pinto@virtualopensystems.com>
To: virtio-dev@lists.oasis-open.org
Cc: qemu-devel@nongnu.org, b.reynal@virtualopensystems.com,
tech@virtualopensystems.com, Claudio.Fontana@huawei.com,
Jani.Kokkonen@huawei.com,
Christian Pinto <c.pinto@virtualopensystems.com>
Subject: [Qemu-devel] [virtio-dev][RFC 1/2] content: reserve virtio device ID
Date: Fri, 17 Jun 2016 18:03:13 +0200 [thread overview]
Message-ID: <1466179394-4744-2-git-send-email-c.pinto@virtualopensystems.com> (raw)
In-Reply-To: <1466179394-4744-1-git-send-email-c.pinto@virtualopensystems.com>
Signed-off-by: Christian Pinto <c.pinto@virtualopensystems.com>
---
content.tex | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/content.tex b/content.tex
index d989d98..0d98926 100644
--- a/content.tex
+++ b/content.tex
@@ -2990,6 +2990,8 @@ Device ID & Virtio Device \\
\hline
18 & Input device \\
\hline
+19 & Signal Distribution Module \\
+\hline
\end{tabular}
Some of the devices above are unspecified by this document,
@@ -5641,6 +5643,8 @@ descriptor for the \field{sense_len}, \field{residual},
\field{status_qualifier}, \field{status}, \field{response} and
\field{sense} fields.
+\input{virtio-sdm.tex}
+
\chapter{Reserved Feature Bits}\label{sec:Reserved Feature Bits}
Currently there are three device-independent feature bits defined:
--
1.9.1
next prev parent reply other threads:[~2016-06-17 16:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-17 16:03 [Qemu-devel] [virtio-dev][RFC 0/2] Signal Distribution Module virtio device specification Christian Pinto
2016-06-17 16:03 ` Christian Pinto [this message]
2016-06-23 18:57 ` [Qemu-devel] [virtio-dev][RFC 1/2] content: reserve virtio device ID Stefan Hajnoczi
2016-06-24 12:45 ` Christian Pinto
2016-06-24 13:04 ` Cornelia Huck
2016-06-24 14:08 ` Christian Pinto
2016-06-17 16:03 ` [Qemu-devel] [virtio-dev][RFC 2/2] virtio-sdm: new device specification Christian Pinto
2016-06-23 19:39 ` Stefan Hajnoczi
2016-06-24 12:39 ` Christian Pinto
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=1466179394-4744-2-git-send-email-c.pinto@virtualopensystems.com \
--to=c.pinto@virtualopensystems.com \
--cc=Claudio.Fontana@huawei.com \
--cc=Jani.Kokkonen@huawei.com \
--cc=b.reynal@virtualopensystems.com \
--cc=qemu-devel@nongnu.org \
--cc=tech@virtualopensystems.com \
--cc=virtio-dev@lists.oasis-open.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).