qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: xiaoqiang zhao <zxq_yx_007@163.com>
To: Paolo Bonzini <pbonzini@redhat.com>, qemu-devel@nongnu.org
Cc: peter.maydell@linaro.org, agraf@suse.de, michael@walle.cc,
	edgar.iglesias@gmail.com, cornelia.huck@de.ibm.com
Subject: Re: [Qemu-devel] [PATCH v3 2/4] hw/char: QOM'ify etraxfs_ser.c
Date: Wed, 18 May 2016 18:33:38 +0800	[thread overview]
Message-ID: <573C4502.6050206@163.com> (raw)
In-Reply-To: <573B13D1.2070805@redhat.com>


在 2016年05月17日 20:51, Paolo Bonzini 写道:
> I'm sorry, this is not enough.  You need to learn how to test this
> device.  CRIS images are available athttp://wiki.qemu.org/Testing.
>
> You have not added a replacement for the call to
> qemu_char_get_next_serial().  The board code in hw/cris/axis_dev88.c
> needs to use qemu_char_get_next_serial().
>
> I suggest creating a function like
>
>      void etraxfs_ser_create(hwaddr addr, qemu_irq irq,
>                              CharDriverState *chr) {
>          DeviceState *dev;
>          SysBusDevice *s;
>          qemu_irq irq;
>
>          dev = qdev_create(NULL, "extrafs,serial");
>          s = SYS_BUS_DEVICE(dev);
>          qdev_prop_set_chr(s, "chardev", chr);
>          qdev_init_nofail(dev);
>          sysbus_mmio_map(s, 0, addr);
>          sysbus_connect_irq(s, 0, irq);
>      }
  Oh, I see.

  reply	other threads:[~2016-05-18 10:34 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-13  3:07 [Qemu-devel] [PATCH v3 0/4] QOM'ify hw/char devices xiaoqiang zhao
2016-05-13  3:07 ` [Qemu-devel] [PATCH v3 1/4] hw/char: QOM'ify escc.c xiaoqiang zhao
2016-05-13  3:07 ` [Qemu-devel] [PATCH v3 2/4] hw/char: QOM'ify etraxfs_ser.c xiaoqiang zhao
2016-05-17 12:51   ` Paolo Bonzini
2016-05-18 10:33     ` xiaoqiang zhao [this message]
2016-05-13  3:07 ` [Qemu-devel] [PATCH v3 3/4] hw/char: QOM'ify lm32_juart.c xiaoqiang zhao
2016-05-13  3:07 ` [Qemu-devel] [PATCH v3 4/4] hw/char: QOM'ify lm32_uart.c xiaoqiang zhao

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=573C4502.6050206@163.com \
    --to=zxq_yx_007@163.com \
    --cc=agraf@suse.de \
    --cc=cornelia.huck@de.ibm.com \
    --cc=edgar.iglesias@gmail.com \
    --cc=michael@walle.cc \
    --cc=pbonzini@redhat.com \
    --cc=peter.maydell@linaro.org \
    --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).