From: Gerd Hoffmann <kraxel@redhat.com>
To: Alon Levy <alevy@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 1/5] usb-ccid: add CCID bus
Date: Wed, 15 Dec 2010 13:23:11 +0100 [thread overview]
Message-ID: <4D08B32F.1000007@redhat.com> (raw)
In-Reply-To: <1292179059-21617-2-git-send-email-alevy@redhat.com>
On 12/12/10 19:37, Alon Levy wrote:
> A CCID device is a smart card reader. It is a USB device, defined at [1].
> This patch introduces the usb-ccid device that is a ccid bus. Next patches will
> introduce two card types to use it, a passthru card and an emulated card.
Looks good overall, just some minor nits / questions:
> +struct CCIDCardState {
> + DeviceState qdev;
Add "uint32_t slot" here?
Also adding a bus property for it would be good, even though it can't be
anything but '0' right now, to prepare the interfaces for the day when
we'll support more than a single card slot and thus can attach multiple
cards to the ccid bus.
> +static VMStateDescription ccid_vmstate = {
> + .name = CCID_DEV_NAME,
> + .version_id = 1,
> + .minimum_version_id = 1,
> + .post_load = ccid_post_load,
> + .pre_save = ccid_pre_save,
> + .fields = (VMStateField []) {
> + VMSTATE_STRUCT(dev, USBCCIDState, 1, usb_device_vmstate, USBDevice),
Can we please disable this for now? USB migration support doesn't
exist, and when we add it chances are that it isn't compatible with what
you have here.
> +static struct USBDeviceInfo ccid_info = {
> + .product_desc = "QEMU USB CCID",
> + .qdev.name = CCID_DEV_NAME,
> + .qdev.size = sizeof(USBCCIDState),
> + .qdev.vmsd =&ccid_vmstate,
Best leave the vmstate structs in the code (with a comment) and just zap
this line which winds it up.
thanks,
Gerd
next prev parent reply other threads:[~2010-12-15 12:23 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-12 18:37 [Qemu-devel] [PATCH 0/5] usb-ccid (v9) Alon Levy
2010-12-12 18:37 ` [Qemu-devel] [PATCH 1/5] usb-ccid: add CCID bus Alon Levy
2010-12-15 12:23 ` Gerd Hoffmann [this message]
2010-12-12 18:37 ` [Qemu-devel] [PATCH 2/5] ccid: add passthru card device Alon Levy
2010-12-15 12:27 ` Gerd Hoffmann
2010-12-12 18:37 ` [Qemu-devel] [PATCH 3/5] libcacard: initial commit after coding style fixes Alon Levy
2010-12-15 12:32 ` Gerd Hoffmann
2010-12-12 18:37 ` [Qemu-devel] [PATCH 4/5] ccid: add ccid-card-emulated device (v2) Alon Levy
2010-12-15 12:37 ` Gerd Hoffmann
2010-12-12 18:37 ` [Qemu-devel] [PATCH 5/5] smartcard: add docs Alon Levy
2010-12-15 12:39 ` Gerd Hoffmann
2010-12-15 12:01 ` [Qemu-devel] [PATCH 0/5] usb-ccid (v9) Gerd Hoffmann
2010-12-15 13:01 ` Alon Levy
-- strict thread matches above, loose matches on Subject: below --
2010-12-16 11:06 [Qemu-devel] [PATCH 0/5] usb-ccid (v10) Alon Levy
2010-12-16 11:06 ` [Qemu-devel] [PATCH 1/5] usb-ccid: add CCID bus Alon Levy
2010-12-16 12:36 ` Gerd Hoffmann
2010-12-17 19:44 [Qemu-devel] [PATCH 0/5] usb-ccid (v11) Alon Levy
2010-12-17 19:44 ` [Qemu-devel] [PATCH 1/5] usb-ccid: add CCID bus Alon Levy
2011-01-03 16:05 [Qemu-devel] [PATCH 0/5] usb-ccid (v12) Alon Levy
2011-01-03 16:05 ` [Qemu-devel] [PATCH 1/5] usb-ccid: add CCID bus Alon Levy
2011-01-06 13:59 [Qemu-devel] [PATCH 0/5] usb-ccid (v13) Alon Levy
2011-01-06 13:59 ` [Qemu-devel] [PATCH 1/5] usb-ccid: add CCID bus Alon Levy
2011-01-08 10:28 [Qemu-devel] [PATCH 0/5] usb-ccid (v14) Alon Levy
2011-01-08 10:28 ` [Qemu-devel] [PATCH 1/5] usb-ccid: add CCID bus 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=4D08B32F.1000007@redhat.com \
--to=kraxel@redhat.com \
--cc=alevy@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.