From: Blue Swirl <blauwirbel@gmail.com>
To: Hollis Blanchard <hollis@penguinppc.org>
Cc: Baojun Wang <wangbj@gmail.com>,
"Richard W.M. Jones" <rjones@redhat.com>,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] PowerPC 440 support
Date: Mon, 15 Jun 2009 19:52:09 +0300 [thread overview]
Message-ID: <f43fc5580906150952r4df83e59tfed147c9946d4e7c@mail.gmail.com> (raw)
In-Reply-To: <fb412d760906150846l3f38cd9w2d51f7a1733dc7ea@mail.gmail.com>
On 6/15/09, Hollis Blanchard <hollis@penguinppc.org> wrote:
> KVM PPC execution doesn't use firmware today. Instead we create the device
> tree in qemu itself, stuff it into guest memory, and point a guest register
> at it on entry. This was just a shortcut/hack, because we didn't have enough
> time to enable both Linux and uboot.
>
> I agree that the best way to do things long-term is to run u-boot inside the
> guest environment. That will likely require improvements to qemu's device
> emulation, and also we'll probably need to work out a way for qemu to pass
> parameters (e.g. memory size) to u-boot. IMHO, the best approach there would
> be to have u-boot interpret a device tree from qemu, then modify it and pass
> it on to the kernel. Obviously that will require u-boot work.
I'm not familiar with u-boot, could we use OpenBIOS instead? Is u-boot
used on real hardware?
next prev parent reply other threads:[~2009-06-15 16:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-14 17:28 [Qemu-devel] PowerPC 440 support Hollis Blanchard
2009-06-14 18:33 ` Blue Swirl
2009-06-14 19:46 ` Hollis Blanchard
2009-06-14 20:40 ` Blue Swirl
2009-06-15 4:40 ` Baojun Wang
2009-06-15 15:46 ` Hollis Blanchard
2009-06-15 16:52 ` Blue Swirl [this message]
2009-06-15 17:37 ` Hollis Blanchard
2009-06-16 15:12 ` Baojun Wang
2009-06-16 15:36 ` Hollis Blanchard
2009-06-15 4:37 ` Baojun Wang
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=f43fc5580906150952r4df83e59tfed147c9946d4e7c@mail.gmail.com \
--to=blauwirbel@gmail.com \
--cc=hollis@penguinppc.org \
--cc=qemu-devel@nongnu.org \
--cc=rjones@redhat.com \
--cc=wangbj@gmail.com \
/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).