From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1MGFPz-0000tr-QS
	for qemu-devel@nongnu.org; Mon, 15 Jun 2009 12:52:24 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1MGFPr-0000gg-TR
	for qemu-devel@nongnu.org; Mon, 15 Jun 2009 12:52:19 -0400
Received: from [199.232.76.173] (port=33373 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1MGFPr-0000gP-G9
	for qemu-devel@nongnu.org; Mon, 15 Jun 2009 12:52:15 -0400
Received: from fg-out-1718.google.com ([72.14.220.158]:53567)
	by monty-python.gnu.org with esmtp (Exim 4.60)
	(envelope-from <blauwirbel@gmail.com>) id 1MGFPq-0007py-Vu
	for qemu-devel@nongnu.org; Mon, 15 Jun 2009 12:52:15 -0400
Received: by fg-out-1718.google.com with SMTP id l27so492352fgb.8
	for <qemu-devel@nongnu.org>; Mon, 15 Jun 2009 09:52:09 -0700 (PDT)
MIME-Version: 1.0
In-Reply-To: <fb412d760906150846l3f38cd9w2d51f7a1733dc7ea@mail.gmail.com>
References: <fb412d760906141028n65e50602kd6e5fb08a1510fba@mail.gmail.com>
	<f43fc5580906141133q750f4f6dg5e5eda27eeb5d2e8@mail.gmail.com>
	<fb412d760906141246r26e1d09ek6e4a0a13758a0854@mail.gmail.com>
	<3cdfa5bc0906142140nf2a78rf2a07c3185a9614d@mail.gmail.com>
	<fb412d760906150846l3f38cd9w2d51f7a1733dc7ea@mail.gmail.com>
Date: Mon, 15 Jun 2009 19:52:09 +0300
Message-ID: <f43fc5580906150952r4df83e59tfed147c9946d4e7c@mail.gmail.com>
Subject: Re: [Qemu-devel] PowerPC 440 support
From: Blue Swirl <blauwirbel@gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Hollis Blanchard <hollis@penguinppc.org>
Cc: Baojun Wang <wangbj@gmail.com>, "Richard W.M. Jones" <rjones@redhat.com>, qemu-devel@nongnu.org

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?