From: Blue Swirl <blauwirbel@gmail.com>
To: Rob Landley <rob@landley.net>
Cc: devicetree-discuss@lists.ozlabs.org, qemu-devel@nongnu.org,
CE Linux Developers List <celinux-dev@tree.celinuxforum.org>
Subject: Re: [Qemu-devel] CELF Project Proposal - Device tree support for QEMU system emulation.
Date: Sat, 19 Dec 2009 10:54:37 +0000 [thread overview]
Message-ID: <f43fc5580912190254n43a9a60fv38280d3c0c04ec57@mail.gmail.com> (raw)
In-Reply-To: <200912162246.42366.rob@landley.net>
On Thu, Dec 17, 2009 at 4:46 AM, Rob Landley <rob@landley.net> wrote:
> For background of CELF project proposals, see:
>
> http://elinux.org/CELF_Open_Project_Proposal_2010
>
> Summary:
>
> Integrate a flattened device tree parser into the emulator QEMU, so QEMU can
> create board emulations on the fly (at runtime) from the same data files the
> Linux kernel uses to attach drivers to hardware.
>
> Proposer:
>
> Rob Landley
>
> Description:
>
> Currently, the QEMU is emulating system boards via hardwired .c files, which
> explicitly set up the resources for each emulation in a separate C function.
> In theory, QEMU could parse the same device tree data format the Linux kernel
> uses to set up its hardware resources, and then pass hardware resources along
> to kernels it invokes through its built-in bootloader (I.E. with the -kernel
> option). This could allow new boards to be added to qemu simply by supplying
> device tree files at runtime (assuming emulations for the appropriate
> peripherals had already been implemented in QEMU).
In addition to -kernel case, the device tree should be passed to
OpenBIOS, which would generate OF tree from DT. This would be useful
for OSes other than Linux.
Another interesting case is sun4v hypervisor, which uses a similar
device tree. Some DT transformation would be required in QEMU.
prev parent reply other threads:[~2009-12-19 10:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-17 4:46 [Qemu-devel] CELF Project Proposal - Device tree support for QEMU system emulation Rob Landley
2009-12-17 20:29 ` Anthony Liguori
2009-12-22 12:45 ` Paul Brook
2009-12-17 23:14 ` [Qemu-devel] Re: [Celinux-dev] " Tim Bird
2009-12-19 10:54 ` Blue Swirl [this message]
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=f43fc5580912190254n43a9a60fv38280d3c0c04ec57@mail.gmail.com \
--to=blauwirbel@gmail.com \
--cc=celinux-dev@tree.celinuxforum.org \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=qemu-devel@nongnu.org \
--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).