public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Jerry Van Baren <gerald.vanbaren@ge.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] [PATCH] Update libfdt to 7b3fb789d2cd5fed818f439d0c7aed44b9860fab from dtc
Date: Tue, 30 Oct 2007 07:55:03 -0400	[thread overview]
Message-ID: <47271B97.6080208@ge.com> (raw)
In-Reply-To: <F812D664-EDEF-4307-9946-89EDF9B97126@kernel.crashing.org>

Kumar Gala wrote:
> Patch imports libfdt from dtc as of commit 
> 7b3fb789d2cd5fed818f439d0c7aed44b9860fab
> 
> This is a large patch thus located at the following locations:
> 
> http://gate.crashing.org/~galak/0001-Update-libfdt-to-7b3fb789d2cd5fed818f439d0c7aed44b98.patch 
> 
> 
> git.kernel.org:/pub/scm/boot/u-boot/galak/u-boot.git libfdt   
> 
> Signed-off-by: Kumar Gala <galak@kernel.crashing.org>
> ---
>  board/cm5200/cm5200.c             |    2 +-
>  board/freescale/mpc832xemds/pci.c |    2 +-
>  board/freescale/mpc8349emds/pci.c |    4 +-
>  board/freescale/mpc8349itx/pci.c  |    4 +-
>  board/freescale/mpc8360emds/pci.c |    2 +-
>  common/cmd_fdt.c                  |   22 +-
>  common/fdt_support.c              |   30 +--
>  cpu/mpc83xx/cpu.c                 |    4 +-
>  cpu/mpc83xx/pci.c                 |    4 +-
>  include/fdt.h                     |   51 +---
>  include/libfdt.h                  |  386 +++++++++++++++++++++---
>  libfdt/fdt.c                      |   97 +++++-
>  libfdt/fdt_ro.c                   |  609 
> +++++++++++++++++++++++--------------
>  libfdt/fdt_rw.c                   |  129 +++++++--
>  libfdt/fdt_strerror.c             |   54 +++-
>  libfdt/fdt_sw.c                   |   92 ++++--
>  libfdt/fdt_wip.c                  |   89 +++---
>  libfdt/libfdt_internal.h          |   81 ++++-
>  18 files changed, 1173 insertions(+), 489 deletions(-)

Hi Kumar,

Thanks for working on this.  I cleaned up my u-boot-fdt subrepo in 
preparation for the next round of improvements, of which this will be 
the base.

I've been thinking about how best to do the unfork libfdt and how best 
to stay in sync down the road, but I don't have any good ideas other 
than to just do it.  Down the road, we could try to cherrypick just the 
libfdt changes (assuming David and Jon keep libfdt changes distinct from 
dtc changes in their patches), or we can have an Project Orion approach: 
lots of big bangs.
   <http://en.wikipedia.org/wiki/Project_Orion_%28nuclear_propulsion%29>

FWIIW, I thought about doing our unfork via applying libfdt patches from 
the dtc repository - according to my README, I started from commit
   857f54e79f74429af20c2b5ecc00ee98af6a3b8b
which is in there.  Hmmmmm, something to think about.  That would help 
with the size of the patch (one Project Orion patch or a bunch of 
smaller ones), it would be nice for tracking who changed what and why, 
but it will be a fair amount of work (and some scripting) to identify 
the applicable libfdt patches.

gvb

      parent reply	other threads:[~2007-10-30 11:55 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-29 15:42 [U-Boot-Users] [PATCH] Update libfdt to 7b3fb789d2cd5fed818f439d0c7aed44b9860fab from dtc Kumar Gala
2007-10-29 20:19 ` Wolfgang Denk
2007-10-29 20:24   ` Kumar Gala
2007-10-29 20:31     ` Wolfgang Denk
2007-10-30 11:55 ` Jerry Van Baren [this message]

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=47271B97.6080208@ge.com \
    --to=gerald.vanbaren@ge.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