All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hollis Blanchard <hollisb@us.ibm.com>
To: Paul Brook <paul@codesourcery.com>
Cc: qemu-devel@nongnu.org, Aurelien Jarno <aurelien@aurel32.net>
Subject: Re: [Qemu-devel] [6064] Implement device tree support needed for Bamboo emulation
Date: Tue, 16 Dec 2008 15:09:47 +0000	[thread overview]
Message-ID: <1229440187.31337.15.camel@localhost.localdomain> (raw)
In-Reply-To: <200812161230.24052.paul@codesourcery.com>

On Tue, 2008-12-16 at 12:30 +0000, Paul Brook wrote:
> > 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?

As you mention below, libfdt isn't generally available yet, and since
it's possible to make a real firmware work in this environment (in which
case -kernel isn't needed), the code can still be useful.

If you'd prefer to make libfdt mandatory, I'm fine with that.

> > 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.

That was our conclusion, but Anthony never agreed.

FWIW, I have requested that Fedora and Debian package libfdt, and they
agreed in principle, but it's still missing in Fedora 10 for example.

Is the existence of distribution packages a requirement for use, or
should we say "install it by hand into /usr/local"? If it is a
requirement, which versions of which distributions?

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

Oops, that was a holdover from when we *were* importing libfdt source. I
can remove that, or if we want to import a copy of libfdt, I can leave
it.

I doubt anyone has tried to build libfdt on Windows...

-- 
Hollis Blanchard
IBM Linux Technology Center

  reply	other threads:[~2008-12-16 15:09 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
2008-12-16 15:09   ` Hollis Blanchard [this message]
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=1229440187.31337.15.camel@localhost.localdomain \
    --to=hollisb@us.ibm.com \
    --cc=aurelien@aurel32.net \
    --cc=paul@codesourcery.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.