From: Alon Levy <alevy@redhat.com>
To: qemu-devel@nongnu.org
Cc: anthony@codemonkey.cs, alevy@redhat.com
Subject: [Qemu-devel] [PATCH 0/2] usb-ccid (v3)
Date: Sun, 17 Oct 2010 14:31:02 +0200 [thread overview]
Message-ID: <1287318664-6563-1-git-send-email-alevy@redhat.com> (raw)
This patchset adds two new devices, usb-ccid and ccid-card-passthru, providing a CCID implementation as a bus and a simple passthru protocol implementing card requiring a client.
Next patches will add a fully emulated card that can be used standalone to use a local (host side) card reader, and documentation (being revised for the new bus and multiple cards change)
v3 changes:
* split into bus (usb-ccid.c, uses ccid.h) and card (ccid-card-passthru.c).
* removed documentation (being revised).
v2 changed:
* all QSIMPLEQ turned into fixed sized rings
* all allocated buffers turned into fixed size buffers
* added migration support
* added a message to tell client qemu has migrated to ip:port
* for lack of monitor commands ip:port are 0:0, which causes the updated
vscclient to connect to one port higher on the same host. will add monitor
commands in a separate patch. tested with current setup.
Alon Levy (2):
usb-ccid: add CCID bus
ccid: add passthru card device
Makefile.objs | 1 +
configure | 12 +
hw/ccid-card-passthru.c | 284 ++++++++++
hw/ccid.h | 34 ++
hw/usb-ccid.c | 1349 +++++++++++++++++++++++++++++++++++++++++++++++
hw/vscard_common.h | 130 +++++
6 files changed, 1810 insertions(+), 0 deletions(-)
create mode 100644 hw/ccid-card-passthru.c
create mode 100644 hw/ccid.h
create mode 100644 hw/usb-ccid.c
create mode 100644 hw/vscard_common.h
--
1.7.3.1
next reply other threads:[~2010-10-17 12:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-17 12:31 Alon Levy [this message]
2010-10-17 12:31 ` [Qemu-devel] [PATCH 1/2] usb-ccid: add CCID bus Alon Levy
2010-10-22 13:49 ` Markus Armbruster
2010-10-23 15:45 ` Alon Levy
2010-10-17 12:31 ` [Qemu-devel] [PATCH 2/2] ccid: add passthru card device 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=1287318664-6563-1-git-send-email-alevy@redhat.com \
--to=alevy@redhat.com \
--cc=anthony@codemonkey.cs \
--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).