qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Blue Swirl" <blauwirbel@gmail.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Machine config files
Date: Fri, 14 Nov 2008 21:04:09 +0200	[thread overview]
Message-ID: <f43fc5580811141104v3b6296b0i575693ba944badbb@mail.gmail.com> (raw)
In-Reply-To: <200811140332.14093.paul@codesourcery.com>

On 11/14/08, Paul Brook <paul@codesourcery.com> wrote:
> It's come up in other contexts recently, so I think it's worth mentioning that
>  I am currently working on adding a machine config file support to qemu.
>
>  I am focusing on the board setup side of things, rather than the user-level
>  config side.  My goal is to come up with a system that will allow e.g. the
>  entirety of realview.c and gumstix.c to be eliminated.  Currently this is
>  based this round Flattened Device Trees (as used by ppc-linux).
>
>  I have looked at the bits that Fabrice did a while ago. While that contains
>  some good ideas (which I will probably steal!) it is approaching the problem
>  from a somewhat different direction.  FTDs are a much better fit for some of
>  my requirements (e.g. being able to pass the config through to the guest OS).

libfdt looks like an excellent choice for both Sparc32 and Sparc64, I
think the whole OF tree can be represented with it.

The config could be passed using the firmware configuration device.

  parent reply	other threads:[~2008-11-14 19:04 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-14  3:32 [Qemu-devel] Machine config files Paul Brook
2008-11-14 17:54 ` Hollis Blanchard
2008-11-15  6:52   ` David Gibson
2008-11-14 19:04 ` Blue Swirl [this message]
2008-11-14 19:29   ` Anthony Liguori
2008-11-14 19:51     ` Hollis Blanchard
2008-11-14 20:11       ` Anthony Liguori
2008-11-14 21:39         ` Hollis Blanchard
2008-11-14 21:58           ` Anthony Liguori
2008-11-15  0:13             ` Paul Brook
2008-11-15  6:45               ` David Gibson
2008-11-15  6:58       ` David Gibson

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=f43fc5580811141104v3b6296b0i575693ba944badbb@mail.gmail.com \
    --to=blauwirbel@gmail.com \
    --cc=qemu-devel@nongnu.org \
    /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).