From: David Gibson <dwg@au1.ibm.com>
To: Matt Sealey <matt@genesi-usa.com>
Cc: linuxppc-dev@ozlabs.org, Rob Landley <rob@landley.net>
Subject: Re: Building ppc/powerpc kernel to run under QEMU.
Date: Fri, 11 May 2007 11:46:29 +1000 [thread overview]
Message-ID: <20070511014629.GA31705@localhost.localdomain> (raw)
In-Reply-To: <464397B8.408@genesi-usa.com>
On Thu, May 10, 2007 at 11:07:52PM +0100, Matt Sealey wrote:
> QEMU really really wants a PREP kernel, and that stuff's just not in the new
> arch/powerpc tree anymore is it?
qemu is PReP, eh? Well that would explain the not working: PReP
hasn't been ported to arch/powerpc yet. The fact that qemu acts like
a PReP might make doing so rather easier.
> I'd love to see the device tree once QEMU's kernel has booted :D
>
> I wonder.. would it be useful to have a qemu platform in arch/powerpc and
> for someone to start hacking in devices from a non-emulated point of view?
> It seems a bit of a waste in my mind to emulate a network card, serial port
> IDE interface, ADB (yick!) and a VESA graphics adapter in such 'detail' when
> it can be passed back to the emulation somehow through some kind of clever
> call interface (maybe just have the zero page of the emulation contain a
> bunch of 'ports' which are really function calls pointers..?)
Possibly in the long term.
--
David Gibson | I'll have my music baroque, and my code
david AT gibson.dropbear.id.au | minimalist, thank you. NOT _the_ _other_
| _way_ _around_!
http://www.ozlabs.org/~dgibson
next prev parent reply other threads:[~2007-05-11 1:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-10 2:03 Building ppc/powerpc kernel to run under QEMU Rob Landley
2007-05-10 17:28 ` Linas Vepstas
2007-05-10 22:07 ` Matt Sealey
2007-05-11 1:46 ` David Gibson [this message]
2007-05-12 3:30 ` Rob Landley
2007-05-12 1:46 ` Rob Landley
2007-05-12 3:00 ` Doug Maxey
2007-05-12 4:05 ` Rob Landley
2007-05-12 1:14 ` Rob Landley
2007-05-14 19:09 ` Hollis Blanchard
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=20070511014629.GA31705@localhost.localdomain \
--to=dwg@au1.ibm.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=matt@genesi-usa.com \
--cc=rob@landley.net \
/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).