On Mon, Sep 14, 2009 at 4:55 AM, Paul Hartke
<phartke@xxxxxxxxxxxx> wrote:
I'm familiar with QEMU from other contexts but the Microblaze support. If you (and others) can share, I'm interested in how you are applying it and what problems it is helping to address.
One of the major innovations in the recent MicroBlaze kernels is the use of device trees - an abstract representation of the physical hardware system that is passed to the kernel at boot time to describe the complete hardware platform. We've done the QEMU support for MicroBlaze so that the QEMU simulation model is itself driven by the same flat device tree, so you can simulate arbitrary MicroBlaze systems, address maps etc, driven by the same device tree as the kernel.