From: Thayne Harbaugh <thayne@realmsys.com>
To: daimon55@free.fr, qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] Re: Re: Open Hack'Ware test image.
Date: Tue, 22 Feb 2005 16:14:20 -0700 [thread overview]
Message-ID: <1109114060.6488.27.camel@localhost.localdomain> (raw)
In-Reply-To: <pan.2005.02.22.21.53.23.84728@reply.to>
On Tue, 2005-02-22 at 22:53 +0100, Ronald wrote:
> Le Tue, 22 Feb 2005 14:02:35 -0700, Thayne Harbaugh a écrit :
>
> > You shouldn't even worry about making
> > PReP unstable by adding support for the PCI host bridge to either qemu or
> > OHW because PReP isn't stable now - it doesn't even boot without the host
> > bridge.
>
> Sorry but prep works fine for me, that's even the only ppc emulation mode
> I can use.
You've applied the "Raven" host bridge patch and it breaks your PReP?
Until someone can tell me that having a correct PCI host bridge actually
breaks something I'll continue to ask that the patch be applied. I
believe fixes some problems and that even in the working situations it
makes things more correct. Real PReP hardware has a PCI host bridge -
whether it's the Motorola Raven, Eagle, Grackle or whatever.
If someone can show that having a correct PCI host bridge breaks
something then I'll either rework the patch or drop it. I know that I
have created some broken patches before (HFS comes to mind) and I don't
have a problem rethinking.
next prev parent reply other threads:[~2005-02-22 23:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-22 11:45 [Qemu-devel] Open Hack'Ware test image J. Mayer
2005-02-22 15:07 ` [Qemu-devel] " Ronald
2005-02-22 18:20 ` Thayne Harbaugh
2005-02-22 18:58 ` Fabrice Bellard
2005-02-22 21:02 ` Thayne Harbaugh
2005-02-22 21:53 ` [Qemu-devel] " Ronald
2005-02-22 23:14 ` Thayne Harbaugh [this message]
2005-02-23 2:54 ` J. Mayer
2005-02-22 22:01 ` [Qemu-devel] " J. Mayer
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=1109114060.6488.27.camel@localhost.localdomain \
--to=thayne@realmsys.com \
--cc=daimon55@free.fr \
--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).