All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jerry Van Baren <gerald.vanbaren@smiths-aerospace.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] [PATCH/RFC] mpc5200: switch to CONFIG_OF_LIBFDT
Date: Tue, 04 Sep 2007 08:39:40 -0400	[thread overview]
Message-ID: <46DD520C.7010007@smiths-aerospace.com> (raw)
In-Reply-To: <fa686aa40709032009h3e4307b0x3a974f0711ae461f@mail.gmail.com>

Grant Likely wrote:
> On 9/3/07, Jerry Van Baren <vanbargw@gmail.com> wrote:
>> Hi Grant,
>>
>> The libfdt custodian repo is on the denx.de site, but should be the same
>> as the mainline.  I would say patch your 5xxx custodian repo, publishing
>> the new functions that impact the libfdt stuff as a separate patch and
>> The List can discuss them.  I'll "ack" them and apply them to my repo as
>> well, but NBD.  I will plan on updating the 83xx implementation(s) and
>> publish them for Kim to ack/adopt as well.
> 
> Ah, okay.  I was more wondering if there was a libfdt repo that was
> upstream and separate from u-boot (as dtc uses libfdt also).  Okay,
> I'll rebase against wd's mainline and repost ASAP.
> 
> Cheers,
> g.

Ahh, now I see what you were asking.  When I ported libfdt to u-boot, I 
ended up forking it because the official libfdt did not have all the 
functionality we needed and, at the time, David Gibson was not taking 
patches.  He was working on setting up a dual-licensing for libfdt and 
did not want changes before the lawyers were happy with the licensing.

David has since slain the licensing dragon, but we have not unforked libfdt.

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: David added a BSD license.  Most of the new code 
is from me, but some is from others (Wolfgang G.) and some of it was 
shamelessly stolen from linux's FDT support (not LIBFDT).  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).

Best regards,
gvb

  parent reply	other threads:[~2007-09-04 12:39 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 [this message]
2007-09-04 14:46                   ` Jon Loeliger
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=46DD520C.7010007@smiths-aerospace.com \
    --to=gerald.vanbaren@smiths-aerospace.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 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.