From: Jon Loeliger <jdl@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] [PATCH/RFC] mpc5200: switch to CONFIG_OF_LIBFDT
Date: Tue, 04 Sep 2007 09:46:45 -0500 [thread overview]
Message-ID: <1188917205.624.3.camel@ld0161-tx32> (raw)
In-Reply-To: <46DD520C.7010007@smiths-aerospace.com>
On Tue, 2007-09-04 at 07:39, Jerry Van Baren wrote:
> Ahh, now I see what you were asking. When I ported libfdt to u-boot, I
> ended up forking it
...
> To unfork, we have a couple of issues to work out. One is the amount of
> effort to undo the divergence (probably not bad). The other is the
> dual-licensing issue:
...
> In order to
> unfork, we would have to have agreement from the authors of the
> additional code to relicense with the dual license... or maybe Jon and
> David have independently written equivalent routines (quite possible).
Right.
Jon has recently been busy staring into Cardiac ICUs, getting
a split tooth repaired, and breaking his big toe. No actual
coding is taking place, unfortunately. :-)
jdl
PS -- All I need now is someone to staring using "u" instead of "you"
to set me off...
next prev parent reply other threads:[~2007-09-04 14:46 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-30 18:20 [U-Boot-Users] [PATCH/RFC] mpc5200: switch to CONFIG_OF_LIBFDT Grant Likely
2007-08-30 21:57 ` Kim Phillips
2007-08-30 22:33 ` Grant Likely
2007-08-31 17:39 ` Grant Likely
2007-09-03 20:23 ` Bartlomiej Sieka
2007-09-03 21:50 ` Grant Likely
2007-09-03 20:36 ` Bartlomiej Sieka
2007-09-03 21:47 ` Grant Likely
2007-09-03 21:59 ` Jerry Van Baren
2007-09-03 22:09 ` Grant Likely
2007-09-03 22:40 ` Jerry Van Baren
2007-09-03 22:55 ` Grant Likely
2007-09-04 0:18 ` Jerry Van Baren
2007-09-04 3:09 ` Grant Likely
2007-09-04 4:14 ` Grant Likely
2007-09-04 12:39 ` Jerry Van Baren
2007-09-04 14:46 ` Jon Loeliger [this message]
2007-09-04 14:48 ` Jon Loeliger
2007-09-04 14:48 ` Grant Likely
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=1188917205.624.3.camel@ld0161-tx32 \
--to=jdl@freescale.com \
--cc=u-boot@lists.denx.de \
/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