From: Peter Maydell <peter.maydell@linaro.org>
To: Vasily Khoruzhick <anarsoul@gmail.com>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH v4 2/2] Add support for Zipit Z2 machine
Date: Fri, 24 Jun 2011 15:45:06 +0100 [thread overview]
Message-ID: <BANLkTim3k_RkYO=jH5QsScYNoG_rjKcFxw@mail.gmail.com> (raw)
In-Reply-To: <1308305077-21503-2-git-send-email-anarsoul@gmail.com>
On 17 June 2011 11:04, Vasily Khoruzhick <anarsoul@gmail.com> wrote:
> Zipit Z2 is small PXA270 based handheld.
>
> Signed-off-by: Vasily Khoruzhick <anarsoul@gmail.com>
These patches are affected by the bug in current qemu master
which breaks cpu_physical_memory_map() so I haven't tested them yet.
Some minor nitpicks (nearly there now):
> + if (z->cur_reg == 0x22 && val == 0x0000) {
> + z->enabled = 1;
> + printf("%s: LCD enabled\n", __func__);
> + } else if (z->cur_reg == 0x10 && val == 0x0000) {
> + z->enabled = 0;
> + printf("%s: LCD disabled\n", __func__);
> + }
Drop or use DPRINTF for these printfs, please.
> + break;
> + default:
> + fprintf(stderr, "%s: unknown command!\n", __func__);
Ditto.
> +static VMStateDescription vmstate_zipit_lcd_state = {
> + .name = "zipit-lcd",
> + .version_id = 1,
> + .minimum_version_id = 1,
> + .minimum_version_id_old = 1,
> + .fields = (VMStateField[]) {
> + VMSTATE_INT32(enabled, ZipitLCD),
> + VMSTATE_END_OF_LIST(),
> + }
> +};
This is missing fields for selected, buf[] and cur_reg.
> + if (s->len++ > 2) {
> + fprintf(stderr, "%s: message too long (%i bytes)\n",
> + __func__, s->len);
> + return 1;
> + }
DPRINTF.
> + case I2C_START_RECV:
> + if (s->len != 1) {
> + fprintf(stderr, "%s: short message!?\n", __func__);
> + }
> + break;
Ditto.
> +static VMStateDescription vmstate_aer915_state = {
> + .name = "aer915",
> + .version_id = 1,
> + .minimum_version_id = 1,
> + .minimum_version_id_old = 1,
> + .fields = (VMStateField[]) {
> + VMSTATE_END_OF_LIST(),
> + }
> +};
Missing fields for len and buf[].
Looks ok otherwise. (Patch 1 looks ok too.)
Have you tried vmload/vmsave, by the way? (I don't know if all the
devices the pxa2xx uses have save/load support implemented, it
would be interesting to check if you haven't already.)
-- PMM
next prev parent reply other threads:[~2011-06-24 14:57 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-31 14:16 [Qemu-devel] [PATCH 1/2] pxa2xx_lcd: add proper rotation support Vasily Khoruzhick
2011-05-31 14:16 ` [Qemu-devel] [PATCH 2/2] Add support for Zipit Z2 machine Vasily Khoruzhick
2011-05-31 23:35 ` Peter Maydell
2011-06-01 6:25 ` Vasily Khoruzhick
2011-06-01 9:28 ` [Qemu-devel] [PATCH v2 1/2] pxa2xx_lcd: add proper rotation support Vasily Khoruzhick
2011-06-01 9:28 ` [Qemu-devel] [PATCH v2 2/2] Add support for Zipit Z2 machine Vasily Khoruzhick
2011-06-03 15:33 ` [Qemu-devel] [PATCH v2 1/2] pxa2xx_lcd: add proper rotation support Vasily Khoruzhick
2011-06-03 15:36 ` [Qemu-devel] [PATCH v3 " Vasily Khoruzhick
2011-06-03 15:36 ` [Qemu-devel] [PATCH v3 2/2] Add support for Zipit Z2 machine Vasily Khoruzhick
2011-06-03 15:38 ` [Qemu-devel] [PATCH v3 1/2] pxa2xx_lcd: add proper rotation support Vasily Khoruzhick
2011-06-08 8:52 ` Vasily Khoruzhick
2011-06-08 9:50 ` Peter Maydell
2011-06-08 11:22 ` Vasily Khoruzhick
2011-06-17 10:04 ` [Qemu-devel] [PATCH v4 " Vasily Khoruzhick
2011-06-17 10:04 ` [Qemu-devel] [PATCH v4 2/2] Add support for Zipit Z2 machine Vasily Khoruzhick
2011-06-21 9:47 ` Vasily Khoruzhick
2011-06-24 14:45 ` Peter Maydell [this message]
2011-06-24 17:06 ` Vasily Khoruzhick
2011-06-24 17:16 ` Peter Maydell
2011-07-06 13:52 ` [Qemu-devel] [PATCH v5] " Vasily Khoruzhick
2011-07-11 15:26 ` Vasily Khoruzhick
2011-07-28 8:19 ` Vasily Khoruzhick
2011-07-12 17:31 ` Peter Maydell
2011-07-30 5:04 ` andrzej zaborowski
2011-06-21 9:47 ` [Qemu-devel] [PATCH v4 1/2] pxa2xx_lcd: add proper rotation support Vasily Khoruzhick
2011-07-04 20:11 ` andrzej zaborowski
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='BANLkTim3k_RkYO=jH5QsScYNoG_rjKcFxw@mail.gmail.com' \
--to=peter.maydell@linaro.org \
--cc=anarsoul@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).