From: Anthony Liguori <anthony@codemonkey.ws>
To: Gerd Hoffmann <kraxel@redhat.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 0/2] add pci-serial device.
Date: Tue, 25 Sep 2012 18:43:53 -0500 [thread overview]
Message-ID: <873925sm6e.fsf@codemonkey.ws> (raw)
In-Reply-To: <1348486090-21177-1-git-send-email-kraxel@redhat.com>
Gerd Hoffmann <kraxel@redhat.com> writes:
> Hi,
>
> Two patches, first split up serial.c a bit,
> then actually add the pci-based serial device.
The series looks good to me. A couple requests:
1) Could you add a spec describing this new PCI device? Doesn't need to
be more than a couple paragraphs since the device is super simple.
2) Could you make the inf file an separate patch and either include
documentation in the commit message on how to use it with Windows or
just add a comment to the inf file?
This is a new PCI space for QEMU too. Is this a driver that is "owned"
by QEMU and Red Hat is donating the PCI id or is this a driver that RH
controls that we're implementing?
The only reason I ask is whether this is something we can add new
features to. I can't think of one off hand, but it can't hurt to work
this out up front.
Regards,
Anthony Liguori
>
> cheers,
> Gerd
>
> Gerd Hoffmann (2):
> serial: split serial.c
> serial: add pci variant
>
> default-configs/pci.mak | 2 +
> docs/pciserial.inf | 96 +++++++++++++++++++++++++++++++
> hw/Makefile.objs | 3 +-
> hw/alpha_dp264.c | 1 +
> hw/kzm.c | 2 +-
> hw/mips_fulong2e.c | 1 +
> hw/mips_jazz.c | 1 +
> hw/mips_malta.c | 1 +
> hw/mips_mipssim.c | 2 +-
> hw/mips_r4k.c | 1 +
> hw/musicpal.c | 2 +-
> hw/omap_uart.c | 3 +-
> hw/openrisc_sim.c | 3 +-
> hw/pc.c | 1 +
> hw/pc.h | 27 ---------
> hw/pci_ids.h | 1 +
> hw/petalogix_ml605_mmu.c | 2 +-
> hw/ppc/e500.c | 2 +-
> hw/ppc405_uc.c | 2 +-
> hw/ppc440_bamboo.c | 2 +-
> hw/ppc_prep.c | 1 +
> hw/pxa2xx.c | 2 +-
> hw/serial-isa.c | 130 +++++++++++++++++++++++++++++++++++++++++
> hw/serial-pci.c | 101 ++++++++++++++++++++++++++++++++
> hw/serial.c | 143 ++--------------------------------------------
> hw/serial.h | 73 +++++++++++++++++++++++
> hw/sm501.c | 2 +-
> hw/sun4u.c | 1 +
> hw/virtex_ml507.c | 2 +-
> hw/xtensa_lx60.c | 3 +-
> 30 files changed, 433 insertions(+), 180 deletions(-)
> create mode 100644 docs/pciserial.inf
> create mode 100644 hw/serial-isa.c
> create mode 100644 hw/serial-pci.c
> create mode 100644 hw/serial.h
next prev parent reply other threads:[~2012-09-25 23:44 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-24 11:28 [Qemu-devel] [PATCH 0/2] add pci-serial device Gerd Hoffmann
2012-09-24 11:28 ` [Qemu-devel] [PATCH 1/2] serial: split serial.c Gerd Hoffmann
2012-09-24 11:28 ` [Qemu-devel] [PATCH 2/2] serial: add pci variant Gerd Hoffmann
2012-09-25 23:43 ` Anthony Liguori [this message]
2012-09-26 0:18 ` [Qemu-devel] [PATCH 0/2] add pci-serial device Jan Kiszka
2012-09-26 6:54 ` Gerd Hoffmann
2012-09-26 6:44 ` Gerd Hoffmann
2012-09-26 13:01 ` Anthony Liguori
2012-09-27 5:53 ` Gerd Hoffmann
2012-09-28 10:06 ` Michael S. Tsirkin
2012-09-28 11:45 ` Gerd Hoffmann
2012-09-28 10:07 ` Michael S. Tsirkin
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=873925sm6e.fsf@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=kraxel@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).