qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Anthony Liguori <anthony@codemonkey.ws>
To: Gleb Natapov <gleb@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 1/5] Keep track of ISA ports ISA device is using in qdev.
Date: Tue, 26 Oct 2010 08:25:14 -0500	[thread overview]
Message-ID: <4CC6D6BA.8000007@codemonkey.ws> (raw)
In-Reply-To: <1288090091-25874-2-git-send-email-gleb@redhat.com>

On 10/26/2010 05:48 AM, Gleb Natapov wrote:
> Store all io ports used by device in ISADevice structure.
>
> Signed-off-by: Gleb Natapov<gleb@redhat.com>
> ---
>   hw/cs4231a.c     |    1 +
>   hw/fdc.c         |    3 +++
>   hw/gus.c         |    4 ++++
>   hw/ide/isa.c     |    2 ++
>   hw/isa-bus.c     |   25 +++++++++++++++++++++++++
>   hw/isa.h         |    4 ++++
>   hw/m48t59.c      |    1 +
>   hw/mc146818rtc.c |    1 +
>   hw/ne2000-isa.c  |    3 +++
>   hw/parallel.c    |    5 +++++
>   hw/pckbd.c       |    3 +++
>   hw/sb16.c        |    4 ++++
>   hw/serial.c      |    1 +
>   13 files changed, 57 insertions(+), 0 deletions(-)
>
> diff --git a/hw/cs4231a.c b/hw/cs4231a.c
> index 4d5ce5c..598f032 100644
> --- a/hw/cs4231a.c
> +++ b/hw/cs4231a.c
> @@ -645,6 +645,7 @@ static int cs4231a_initfn (ISADevice *dev)
>       isa_init_irq (dev,&s->pic, s->irq);
>
>       for (i = 0; i<  4; i++) {
> +        isa_init_ioport(dev, i);
>           register_ioport_write (s->port + i, 1, 1, cs_write, s);
>           register_ioport_read (s->port + i, 1, 1, cs_read, s);
>    

A better way to do this would be to introduce isa_register_ioport.

We can take Avi's series first since that probably makes this easier to 
implement.

Regards,

Anthony Liguori

  reply	other threads:[~2010-10-26 13:25 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-26 10:48 [Qemu-devel] [PATCH 0/5] boot order specification Gleb Natapov
2010-10-26 10:48 ` [Qemu-devel] [PATCH 1/5] Keep track of ISA ports ISA device is using in qdev Gleb Natapov
2010-10-26 13:25   ` Anthony Liguori [this message]
2010-10-26 13:30     ` Gleb Natapov
2010-10-26 13:32       ` Anthony Liguori
2010-10-26 15:42   ` Blue Swirl
2010-10-26 10:48 ` [Qemu-devel] [PATCH 2/5] Add get_dev_path callback to ISA bus " Gleb Natapov
2010-10-26 10:48 ` [Qemu-devel] [PATCH 3/5] Store IDE bus id in IDEBus structure for easy access Gleb Natapov
2010-10-26 10:48 ` [Qemu-devel] [PATCH 4/5] Add get_dev_path callback to IDE bus Gleb Natapov
2010-10-26 10:48 ` [Qemu-devel] [PATCH 5/5] Add bootindex parameter to net/block/fd device Gleb Natapov
2010-10-26 13:29   ` Anthony Liguori
2010-10-26 14:16     ` Gleb Natapov
2010-10-26 12:40 ` [Qemu-devel] [PATCH 0/5] boot order specification Bernhard Kohl
2010-10-26 13:07   ` Gleb Natapov
2010-10-26 13:35     ` Bernhard Kohl
2010-10-26 13:38       ` Gleb Natapov
2010-10-26 15:35 ` Blue Swirl
2010-10-26 15:43   ` Gleb Natapov
2010-10-26 17:00     ` Blue Swirl
2010-10-26 19:35       ` Gleb Natapov
2010-10-26 19:57         ` Blue Swirl
2010-10-26 20:34           ` Gleb Natapov
2010-10-26 20:49             ` Blue Swirl
2010-10-26 21:02               ` Gleb Natapov
2010-10-26 21:14             ` Scott Wood
2010-10-27  8:57               ` Gleb Natapov
2010-10-27 16:39                 ` Scott Wood

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=4CC6D6BA.8000007@codemonkey.ws \
    --to=anthony@codemonkey.ws \
    --cc=gleb@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).