qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Weil <weil@mail.berlios.de>
To: Avi Kivity <avi@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] mips_malta: move i8259 initialization	after piix4 initialization
Date: Thu, 15 Sep 2011 07:56:47 +0200	[thread overview]
Message-ID: <4E71939F.8050400@mail.berlios.de> (raw)
In-Reply-To: <4E709763.1080805@redhat.com>

Am 14.09.2011 14:00, schrieb Avi Kivity:
> On 09/12/2011 04:07 PM, Avi Kivity wrote:
>> i8259 is an ISA device (or at least, depends on the ISA 
>> infrastructure to
>> register its ioport); and the ISA bus is supplied by piix4.  Later 
>> patches
>> make this dependency explicit.
>>
>> Move the i8259 initialization until after the ISA bus is created; and 
>> supply
>> a new qemu_irq to PCI initialization, since the i8259 isn't ready 
>> yet.  Later
>> wire the new qemu_irq to the i8259.
>>
>
> Can this please be reviewed?  It's in the front of the memory queue 
> logjam.
>

Tested-by: Stefan Weil <weil@mail.berlios.de>

Test configurations:

1. Debian lenny, qemu-system-mipsel (32 bit little endian), MIPS Malta
2. Debian lenny, qemu-system-mips64 (64 bit big endian), MIPS Malta

Both work on a i386 linux host with the patch applied.

  parent reply	other threads:[~2011-09-15  5:56 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-12 13:07 [Qemu-devel] [PATCH] mips_malta: move i8259 initialization after piix4 initialization Avi Kivity
2011-09-14 12:00 ` Avi Kivity
2011-09-14 16:19   ` Andreas Färber
2011-09-14 19:03     ` Stefan Weil
2011-09-14 20:17     ` Avi Kivity
2011-09-14 20:52       ` Edgar E. Iglesias
2011-09-15  5:23         ` Stefan Weil
2011-09-18 12:04         ` Avi Kivity
2011-09-15  5:56   ` Stefan Weil [this message]
2011-09-14 20:32 ` Richard Henderson
2011-09-14 20:37   ` Avi Kivity
2011-09-14 20:40     ` Richard Henderson
2011-09-16 13:19 ` Anthony Liguori

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=4E71939F.8050400@mail.berlios.de \
    --to=weil@mail.berlios.de \
    --cc=avi@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).