From: Hollis Blanchard <hollisb@us.ibm.com>
To: jyoung5@us.ibm.com
Cc: kvm-devel <kvm-devel@lists.sourceforge.net>,
Avi Kivity <avi@qumranet.com>
Subject: Re: Top level kvm-userspace directory getting crowded ... need new dir for qemu dependencies
Date: Wed, 27 Feb 2008 10:29:32 -0600 [thread overview]
Message-ID: <1204129772.2532.31.camel@basalt> (raw)
In-Reply-To: <1204046679.6589.8.camel@thinkpad.austin.ibm.com>
On Tue, 2008-02-26 at 11:24 -0600, Jerone Young wrote:
>
> > However, why do we need libfdt? Is it not carried by distros, or do
> you
> > need to make changes?
>
> Well it actually isn't distributed with each distro .. sigh ..
> actually
> this comes from a tool called dtc, compiles/decompiles a device tree.
> Even the linux kernel has it's own version of libfdt ... so it's not
> exactly a central coordinated effort. It's something that kind of gets
> passed from project to project but never stand alone. So we kind of
> have
> to do the same.
It is a centrally co-ordinated effort, but it is not a package a distro
would carry. It is code shared by anything that needs to load a PowerPC
Linux kernel, for example: the kernel bootwrapper (part of the Linux
source tree), u-boot firmware, Xend, and now qemu.
Accordingly, a libfdt.rpm simply doesn't make sense, and the code is
intended to be copied into any codebase that needs it.
--
Hollis Blanchard
IBM Linux Technology Center
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
next prev parent reply other threads:[~2008-02-27 16:29 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-25 6:50 Top level kvm-userspace directory getting crowded ... need new dir for qemu dependencies Jerone Young
2008-02-25 9:00 ` Avi Kivity
2008-02-26 17:24 ` Jerone Young
2008-02-27 10:59 ` Avi Kivity
2008-02-27 16:29 ` Hollis Blanchard [this message]
2008-02-27 16:34 ` Avi Kivity
2008-02-27 16:48 ` Alexander Graf
2008-02-27 16:59 ` Avi Kivity
2008-02-27 17:07 ` Alexander Graf
2008-02-27 18:56 ` Hollis Blanchard
2008-02-27 19:18 ` Alexander Graf
2008-02-27 20:22 ` [kvm-ppc-devel] " Hollis Blanchard
2008-02-27 21:20 ` Alexander Graf
2008-02-27 22:19 ` Hollis Blanchard
2008-02-27 22:32 ` Alexander Graf
2008-03-02 18:38 ` Luca Barbato
2008-02-27 19:25 ` Avi Kivity
2008-02-27 19:57 ` [kvm-ppc-devel] " Hollis Blanchard
2008-02-28 8:16 ` Avi Kivity
2008-02-28 20:28 ` Jerone Young
2008-03-02 16:41 ` Avi Kivity
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=1204129772.2532.31.camel@basalt \
--to=hollisb@us.ibm.com \
--cc=avi@qumranet.com \
--cc=jyoung5@us.ibm.com \
--cc=kvm-devel@lists.sourceforge.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