From: Jerry Van Baren <gvb.linuxppc.dev@gmail•com>
To: jyoung5@us•ibm.com
Cc: linuxppc-dev <linuxppc-dev@ozlabs•org>, David Gibson <dwg@au1•ibm.com>
Subject: Re: [dtc] breaking out libfdt from dtc so other progs can use it
Date: Thu, 28 Feb 2008 21:53:43 -0500 [thread overview]
Message-ID: <47C773B7.40302@gmail.com> (raw)
In-Reply-To: <1204228953.12181.15.camel@thinkpad.austin.ibm.com>
Jerone Young wrote:
> On Thu, 2008-02-28 at 12:59 -0600, Josh Boyer wrote:
>> On Thu, 28 Feb 2008 10:30:44 -0600
>> Jerone Young <jyoung5@us•ibm.com> wrote:
[big snip]
>> You still haven't explained why maintenance is harder or somehow less
>> doable by having it in the dtc repo. Maintenance is very much the
>> concern of the upstream developers, which seem to be saying it's not a
>> problem for them...
>
> I guess what I see libfdt as something like shared userspace library. At
> the moment dtc is the only userspace project to use it. So it make
> perfect since to keep it with the source and not separated.
>
> Though when other projects need it .. the option of having to try to
> figure out what version of dtc to grab so understand what libfdt is
> usable, can be a bit of a pain.
>
> Though I can't really argue that you can't get around this by just
> downloading dtc and grabbing out the libfdt package..though it does
> cause some indirection.
FWIIW, that is what the u-boot project is doing. The last pass, I
actually extracted the libfdt git patch(es) and then applied them to the
u-boot tree so that the history would be carried over. The libfdt
portion is now quite stable and I don't see major changes coming that
would cause this methodology to be a problem.
Best regards,
gvb
next prev parent reply other threads:[~2008-02-29 2:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-27 19:40 [dtc] breaking out libfdt from dtc so other progs can use it Jerone Young
2008-02-27 20:31 ` Josh Boyer
2008-02-27 21:24 ` Jerone Young
2008-02-28 1:41 ` David Gibson
2008-02-28 16:30 ` Jerone Young
2008-02-28 18:59 ` Josh Boyer
2008-02-28 20:02 ` Jerone Young
2008-02-29 2:53 ` Jerry Van Baren [this message]
2008-02-29 8:35 ` Geert Uytterhoeven
2008-02-29 14:09 ` Josh Boyer
2008-03-01 9:12 ` Fathi Boudra
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=47C773B7.40302@gmail.com \
--to=gvb.linuxppc.dev@gmail$(echo .)com \
--cc=dwg@au1$(echo .)ibm.com \
--cc=jyoung5@us$(echo .)ibm.com \
--cc=linuxppc-dev@ozlabs$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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