From: Alon Levy <alevy@redhat.com>
To: qemu-devel@nongnu.org
Cc: blauwirbel@gmail.com
Subject: [Qemu-devel] [PATCH 0/1] add spicevmc chardev
Date: Wed, 19 Jan 2011 10:49:49 +0200 [thread overview]
Message-ID: <1295426990-3546-1-git-send-email-alevy@redhat.com> (raw)
In additional to the description in the patch, see following email for uses:
http://lists.nongnu.org/archive/html/qemu-devel/2011-01/msg01208.html
In particular it would/could be used for:
current vdagent of spice uses this for mouse, copy paste
proposed smartcard device for qemu uses this with spice
usb forwarding
terminal forwarding
qemu monitor forwarding
Alon Levy (1):
spice: add chardev (v5)
Makefile.objs | 2 +-
qemu-char.c | 4 +
qemu-config.c | 6 ++
qemu-options.hx | 16 ++++-
spice-qemu-char.c | 190 +++++++++++++++++++++++++++++++++++++++++++++++++++++
trace-events | 6 ++
ui/qemu-spice.h | 3 +
7 files changed, 225 insertions(+), 2 deletions(-)
create mode 100644 spice-qemu-char.c
--
1.7.3.4
next reply other threads:[~2011-01-19 8:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-19 8:49 Alon Levy [this message]
2011-01-19 8:49 ` [Qemu-devel] [PATCH 1/1] spice: add chardev (v5) Alon Levy
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=1295426990-3546-1-git-send-email-alevy@redhat.com \
--to=alevy@redhat.com \
--cc=blauwirbel@gmail.com \
--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).