From: Blue Swirl <blauwirbel@gmail.com>
To: The OpenBIOS Mailinglist <openbios@openbios.org>
Cc: qemu-devel@nongnu.org
Subject: Re: [OpenBIOS] [Qemu-devel] [PATCH, RFC] Mac99 (CHRP?) support
Date: Sat, 7 Feb 2009 18:22:10 +0200 [thread overview]
Message-ID: <f43fc5580902070822i857c2b7t824c27d381605944@mail.gmail.com> (raw)
In-Reply-To: <20090207141803.GA6533@volta.aurel32.net>
On 2/7/09, Aurelien Jarno <aurelien@aurel32.net> wrote:
> On Sat, Feb 07, 2009 at 01:38:58PM +0200, Blue Swirl wrote:
> > Hi,
>
> Hi!
>
> > This set of patches adds basic support for Mac99 Qemu machine,
>
>
> As you ask the question in the subject, this machine is a NewWorld
> machine, and not a CHRP one. I think we don't really want to provide a
> CHRP emulated machine, so the best is probably to rename ppc_chrp.c into
> ppc_newworld.c.
True. I think RS6000 series were closest to CHRP, not iMac.
The rename does not affect OHW status, so it could be done immediately.
> > provided by ppc_chrp.c. I've used the device tree of iMac DV ('99) as
> > reference:
> > http://penguinppc.org/historical/dev-trees-html/imac-dv-99.html
> >
> > The patches changes the machine to use OpenBIOS instead of OHW and
> > otherwise breaks OHW assumptions. On OpenBIOS side there are still
> > some missing bits.
> >
> > Comments welcome.
>
>
> Great work.
>
> I gave a quick look at the patches, they looks fine. However I still
> experience some problem with the PowerMac IDE emulation, especially with
> recent kernels, so until it is fixed (Laurent is working on that) I
> think we should keep the CMD646 as a default.
OK¸ I'll change that part and send new patches.
next prev parent reply other threads:[~2009-02-07 16:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-07 11:38 [Qemu-devel] [PATCH, RFC] Mac99 (CHRP?) support Blue Swirl
2009-02-07 14:18 ` Aurelien Jarno
2009-02-07 16:22 ` Blue Swirl [this message]
2009-02-07 21:05 ` [OpenBIOS] " Blue Swirl
2009-02-08 0:43 ` Natalia Portillo
2009-02-08 7:52 ` Blue Swirl
2009-02-08 10:04 ` Stuart Brady
2009-02-08 14:15 ` Aurelien Jarno
2009-02-08 14:26 ` Christian Brunschen
2009-02-08 17:11 ` Blue Swirl
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=f43fc5580902070822i857c2b7t824c27d381605944@mail.gmail.com \
--to=blauwirbel@gmail.com \
--cc=openbios@openbios.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 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).