From: Blue Swirl <blauwirbel@gmail.com>
To: qemu-devel@nongnu.org
Subject: Re: [OpenBIOS] [Qemu-devel] [PATCH, RFC] Mac99 (CHRP?) support
Date: Sun, 8 Feb 2009 19:11:52 +0200 [thread overview]
Message-ID: <f43fc5580902080911p50ea1dd4of988ce5996c2a712@mail.gmail.com> (raw)
In-Reply-To: <20090208141530.GA9575@volta.aurel32.net>
On 2/8/09, Aurelien Jarno <aurelien@aurel32.net> wrote:
> On Sat, Feb 07, 2009 at 11:05:52PM +0200, Blue Swirl wrote:
> > On 2/7/09, Blue Swirl <blauwirbel@gmail.com> wrote:
> > > 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.
> >
> > This new set of patches perform the rename (to be replaced with SVN
> > operation). CMD646 is used instead of pmac ide.
> >
> > Debian 4.0 R6 cd image boots, installer starts but keyboard does not
> > work (probably because OpenBIOS doesn't advertise OpenPic).
>
>
> That may be the problem. Alternatively, note that NewWorld machine are
> not suppose to support ADB bus, so maybe the kernel is disabling that
> part. We should switch the keyboard and the mouse to USB as on real
> machines. We already have the code on the QEMU side, so it should be
> easy. On the OpenBIOS side the code to support an USB keyboard is
> probably more complicated.
Well, I just found out that even without any USB support in OpenBIOS,
Linux finds the OHCI device and then the keyboard and mouse connected
to it, so keyboard works using the same Debian image.
prev parent reply other threads:[~2009-02-08 17:11 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 ` [OpenBIOS] " Blue Swirl
2009-02-07 21:05 ` 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 [this message]
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=f43fc5580902080911p50ea1dd4of988ce5996c2a712@mail.gmail.com \
--to=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).