From: Paul Brook <paul@codesourcery.com>
To: qemu-devel@nongnu.org
Cc: Blue Swirl <blauwirbel@gmail.com>, Aurelien Jarno <aurelien@aurel32.net>
Subject: Re: [Qemu-devel] arm, mips and mipsel broken
Date: Wed, 11 Nov 2009 18:28:03 +0000 [thread overview]
Message-ID: <200911111828.03660.paul@codesourcery.com> (raw)
In-Reply-To: <20091110213538.GG9052@hall.aurel32.net>
On Tuesday 10 November 2009, Aurelien Jarno wrote:
> On Tue, Nov 10, 2009 at 11:19:40PM +0200, Blue Swirl wrote:
> > On Tue, Nov 10, 2009 at 10:50 PM, Aurelien Jarno <aurelien@aurel32.net>
wrote:
> > > Please note that at least qemu-system-arm, qemu-system-mips and
> > > qemu-system-mipsel are broken by this commit:
> >
> > Given that none of the devices touched by the commit should be used by
> > these targets, the breakage comes from just the single new call to
> > qemu_system_reset in vl.c. This means that the reset functions for
> > those boards and devices must be awfully buggy.
>
> I'll try to have a closer look at the problem tomorrow, if I can't find
> the problem, it's what I'll commit.
This is latent breakage introduced by 45a50b1.
See commits 97fe84f5 (makes breakage obvious) and f2d7497 (fixed ARM).
MIPS still needs fixing.
Paul
next prev parent reply other threads:[~2009-11-11 18:28 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-10 20:50 [Qemu-devel] arm, mips and mipsel broken Aurelien Jarno
2009-11-10 21:19 ` Blue Swirl
2009-11-10 21:35 ` Aurelien Jarno
2009-11-11 18:28 ` Paul Brook [this message]
2009-11-11 21:02 ` Blue Swirl
2009-11-11 21:59 ` Paul Brook
[not found] ` <m3r5s6ndg2.fsf@neno.mitica>
2009-11-11 17:47 ` [Qemu-devel] " Blue Swirl
2009-11-11 18:08 ` Blue Swirl
2009-11-11 18:57 ` [Qemu-devel] " Glauber Costa
2009-11-11 21:00 ` Blue Swirl
2009-11-12 17:34 ` Stefan Weil
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=200911111828.03660.paul@codesourcery.com \
--to=paul@codesourcery.com \
--cc=aurelien@aurel32.net \
--cc=blauwirbel@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).