On 6/15/09, Hollis Blanchard <
address@hidden> 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