qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Thayne Harbaugh <thayne@realmsys.com>
To: qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] Re: Open Hack'Ware test image.
Date: Tue, 22 Feb 2005 14:02:35 -0700	[thread overview]
Message-ID: <1109106155.6488.14.camel@localhost.localdomain> (raw)
In-Reply-To: <421B80C4.50604@bellard.org>

On Tue, 2005-02-22 at 19:58 +0100, Fabrice Bellard wrote:
> Thayne Harbaugh wrote:
> > On Tue, 2005-02-22 at 12:45 +0100, J. Mayer wrote:
> > 
> > 
> >>Note that PREP support has not been checked with this snapshot (but will
> >>be before it'll become a release).
> > 
> > 
> > This won't work because the PCI host bridge *still* hasn't been added to
> > qemu.  I've sent the patch at least twice.  Tha patch hasn't been
> > applied and there hasn't been an explanation as to why it was ignored.
> 
> Hi,
> 
> Sorry for the lack of explanation: I was not sure whether QEMU could 
> work with your patch without an updated PPC BIOS.

Yes, *both* Qemu and OHW need to be patched.  It shouldn't matter which
one supports the host bridge first.  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.

  reply	other threads:[~2005-02-22 21:25 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 [this message]
2005-02-22 21:53       ` [Qemu-devel] " Ronald
2005-02-22 23:14         ` Thayne Harbaugh
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=1109106155.6488.14.camel@localhost.localdomain \
    --to=thayne@realmsys.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).