Update libfdt from device tree compiler (dtc)

Update libfdt to commit 4a5df5c026c96f36326d4037a0658d38193e2ca1 from the device tree compiler (dtc) project.

Signed-off-by Kumar Gala <[email protected]>

---
Note: these patches are also available at:
git.kernel.org:/pub/scm/boot/u-boot/galak/u-boot.git libfdt

Also the patch itself is at:

http://gate.crashing.org/~galak/0003-Update-libfdt-from-device-tree-compiler-dtc.patch

 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                   |  134 +++++++--
 libfdt/fdt_strerror.c             |   54 +++-
 libfdt/fdt_sw.c                   |   92 ++++--
 libfdt/fdt_wip.c                  |   89 +++---
 libfdt/libfdt_internal.h          |   81 ++++-
 18 files changed, 1177 insertions(+), 490 deletions(-)

Thanks, Kumar.

Wolfgang:

How about a compromise on patch publishing: I apply the above patch by pulling it as a single lump from Kumar's repo, but email it broken in two (manually). This would preserve the review concept, since it would be published (and fit through the 40K size filter), but also would actually be in the repo as a single entity, preserving the ability to use git-bisect without inconsistency risks.

How about a compromise on patch publishing: I apply the above patch by pulling it as a single lump from Kumar's repo, but email it broken in two (manually). This would preserve the review concept, since it would be published (and fit through the 40K size filter), but also would actually be in the repo as a single entity, preserving the ability to use git-bisect without inconsistency risks.