qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paul Brook <paul@codesourcery.com>
To: qemu-devel@nongnu.org
Cc: Hollis Blanchard <hollisb@us.ibm.com>,
	Aurelien Jarno <aurelien@aurel32.net>
Subject: Re: [Qemu-devel] [6064] Implement device tree support needed for Bamboo emulation
Date: Tue, 16 Dec 2008 12:30:23 +0000	[thread overview]
Message-ID: <200812161230.24052.paul@codesourcery.com> (raw)
In-Reply-To: <E1LCXP2-0006JS-Or@cvs.savannah.gnu.org>

> To implement the -kernel, -initrd, and -append options, 4xx board emulation
> must load the guest kernel as if firmware had loaded it. Where u-boot would
> be the firmware, we must load the flat device tree into memory and set key
> fields such as /chosen/bootargs.

Then why is it optional?

> This patch introduces a dependency on libfdt for flat device tree support.

I don't like the way this is done.

AFAIK libfdt isn't present in any of the major distros. I thought the 
conclusion was that we should import libfdt into qemu.

Certainly adding libfdt_env.h, which is never used, seems very wrong. I'm 
pretty sure this won't build on win32 either.

Paul

  reply	other threads:[~2008-12-16 12:30 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-16 10:43 [Qemu-devel] [6064] Implement device tree support needed for Bamboo emulation Aurelien Jarno
2008-12-16 12:30 ` Paul Brook [this message]
2008-12-16 15:09   ` Hollis Blanchard
2008-12-16 16:17     ` Anthony Liguori
2008-12-16 16:34       ` Paul Brook
2008-12-16 17:03         ` Blue Swirl
2008-12-16 20:34         ` Thiemo Seufer
2008-12-16 16:31     ` Paul Brook
2008-12-16 16:46     ` Daniel P. Berrange
2008-12-16 17:15       ` Hollis Blanchard
2008-12-16 18:15         ` Josh Boyer

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=200812161230.24052.paul@codesourcery.com \
    --to=paul@codesourcery.com \
    --cc=aurelien@aurel32.net \
    --cc=hollisb@us.ibm.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).