From: Fabrice Bellard <fabrice@bellard.org>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] PPC fixes for qemu/OpenHackWare
Date: Tue, 08 Feb 2005 21:46:22 +0100 [thread overview]
Message-ID: <4209251E.7000807@bellard.org> (raw)
In-Reply-To: <1107891913.14935.17.camel@localhost.localdomain>
Thayne Harbaugh wrote:
> These fixes greatly improve qemu booting on PPC - many Linux
> distributions with kernel 2.4 now work. It's two big patches (one for
> qemu, one for OpenHackWare) - let me know if someone prefers them broken
> out into smaller pieces.
>
> There's still some work to be done to get PREP in good shape as well as
> a Linux 2.6 kernel to work well - expect some more patches in the near
> future.
>
> Highlights
>
> * Real serial
> * Correct PCI host bridge for PREP (wrong in Pearpc, Qemu and
> OpenHackWare)
> * -Werror building for OpenHackWare
> * proper reboot
> * HFS OpenHackWare now correctly traverses the B*tree - greatly improves
> probability of booting *all* HFS based filesystems
> * Many, MANY other fixes
Very good ! Have you looked at Darwin and Mac OS X ? I feel QEMU (and
OpenHackWare) are very close to launch them: at least all the hardware
emulation is there. I am unable to look at the problem because I don't
have an easy way to recompile the Darwin kernel to insert debug
messages... and another problem is that I don't have the time :-)
Fabrice.
next prev parent reply other threads:[~2005-02-08 21:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-08 19:45 [Qemu-devel] PPC fixes for qemu/OpenHackWare Thayne Harbaugh
2005-02-08 20:46 ` Fabrice Bellard [this message]
2005-02-08 21:06 ` Thayne Harbaugh
2005-02-08 22:12 ` Hetz Ben Hamo
2005-02-08 22:11 ` [Qemu-devel] " J. Mayer
2005-02-08 22:25 ` Thayne Harbaugh
2005-02-08 23:32 ` J. Mayer
2005-02-09 18:50 ` [Qemu-devel] " Thayne Harbaugh
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=4209251E.7000807@bellard.org \
--to=fabrice@bellard.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.