From: "Daniel P. Berrange" <berrange@redhat.com>
To: qemu-devel@nongnu.org
Cc: Paul Brook <paul@codesourcery.com>,
Aurelien Jarno <aurelien@aurel32.net>
Subject: Re: [Qemu-devel] [6064] Implement device tree support needed for Bamboo emulation
Date: Tue, 16 Dec 2008 16:46:28 +0000 [thread overview]
Message-ID: <20081216164628.GG20024@redhat.com> (raw)
In-Reply-To: <1229440187.31337.15.camel@localhost.localdomain>
On Tue, Dec 16, 2008 at 03:09:47PM +0000, Hollis Blanchard wrote:
> 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.
If you've got a package review ticket open against Fedora for libfdt
inclusion, let me know the bug number and I'm happy to do the review,
so it is not unduely delayed on its path into Fedora repositories.
I far far prefer to see this kind of thing properly packaged, than
copied into the source tree. Indeed if any application copies another
library's code into their source tree, then when we package that app
for Fedora we typically try to reverse this and make it link against
a proper separately packaged shared library. Copy+paste of libraries
into other apps's source tree is a maintenance disaster, particularly
for security updates.
Regards,
Daniel
--
|: Red Hat, Engineering, London -o- http://people.redhat.com/berrange/ :|
|: http://libvirt.org -o- http://virt-manager.org -o- http://ovirt.org :|
|: http://autobuild.org -o- http://search.cpan.org/~danberr/ :|
|: GnuPG: 7D3B9505 -o- F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 :|
next prev parent reply other threads:[~2008-12-16 16:48 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
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 [this message]
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=20081216164628.GG20024@redhat.com \
--to=berrange@redhat.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 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).