qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Alon Levy <alevy@redhat.com>
To: qemu-devel@nongnu.org
Cc: armbru@redhat.com
Subject: Re: [Qemu-devel] [PATCH 0/4] usb-ccid (v6)
Date: Wed, 17 Nov 2010 13:27:42 +0200	[thread overview]
Message-ID: <20101117112742.GA6875@playa.tlv.redhat.com> (raw)
In-Reply-To: <1289305330-11526-1-git-send-email-alevy@redhat.com>

ping?

On Tue, Nov 09, 2010 at 02:22:06PM +0200, Alon Levy wrote:
> This patchset adds three new devices, usb-ccid, ccid-card-passthru and
> ccid-card-emulated, providing a CCID bus, a simple passthru protocol
> implementing card requiring a client, and a standalone emulated card.
> 
> v5->v6 changes:
>  * really remove static debug (I apologize for claiming to have done so before)
> 
> v4->v5 changes:
>  * rebased to latest
>  * remove static debug in card devices
>  * fix --enable-smartcard to link
>  * stall instead of assert when exceeding BULK_OUT_DATA_SIZE
>  * make ccid_reserve_recv_buf for too large len discard message, not exit
>  * make ccid_reserve_recv_buf return void*
>  * fix typo
>  * remove commented code in VMState
> 
> v3->v4:
>  * remove ccid field in CCIDBus
>  * remove static debug in bus
>  * add back docs
> 
> v2->v3:
>  * split into bus (usb-ccid.c, uses ccid.h) and card (ccid-card-passthru.c).
>  * removed documentation (being revised).
> 
> v1->v2:
>  * 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 (4):
>   usb-ccid: add CCID bus
>   ccid: add passthru card device
>   add ccid-card-emulated device (v2)
>   ccid: add docs
> 
>  Makefile.objs           |    1 +
>  configure               |   33 ++
>  docs/ccid.txt           |  133 +++++
>  hw/ccid-card-emulated.c |  492 +++++++++++++++++
>  hw/ccid-card-passthru.c |  277 ++++++++++
>  hw/ccid.h               |   34 ++
>  hw/usb-ccid.c           | 1342 +++++++++++++++++++++++++++++++++++++++++++++++
>  hw/vscard_common.h      |  130 +++++
>  8 files changed, 2442 insertions(+), 0 deletions(-)
>  create mode 100644 docs/ccid.txt
>  create mode 100644 hw/ccid-card-emulated.c
>  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.2
> 
> 

      parent reply	other threads:[~2010-11-17 11:27 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-09 12:22 [Qemu-devel] [PATCH 0/4] usb-ccid (v6) Alon Levy
2010-11-09 12:22 ` [Qemu-devel] [PATCH 1/4] usb-ccid: add CCID bus Alon Levy
2010-11-09 12:22 ` [Qemu-devel] [PATCH 2/4] ccid: add passthru card device Alon Levy
2010-11-09 12:22 ` [Qemu-devel] [PATCH 3/4] add ccid-card-emulated device (v2) Alon Levy
2010-11-09 12:22 ` [Qemu-devel] [PATCH 4/4] ccid: add docs Alon Levy
2010-11-17 11:27 ` Alon Levy [this message]

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=20101117112742.GA6875@playa.tlv.redhat.com \
    --to=alevy@redhat.com \
    --cc=armbru@redhat.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).