From mboxrd@z Thu Jan  1 00:00:00 1970
From: Jerry Van Baren <gvb.uboot@gmail.com>
Date: Sat, 16 Feb 2008 17:28:47 -0500
Subject: [U-Boot-Users] [PATCH v3] Add sub-commands to fdt
In-Reply-To: <Pine.LNX.4.64.0802151557050.16787@blarg.am.freescale.net>
References: <Pine.LNX.4.64.0802150335580.22869@blarg.am.freescale.net>	<47B607CB.50100@ge.com>	<1D6463B0-3806-444D-8EF5-46CB3B04D696@kernel.crashing.org>
	<Pine.LNX.4.64.0802151557050.16787@blarg.am.freescale.net>
Message-ID: <47B7639F.6070601@gmail.com>
List-Id: <u-boot.lists.denx.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: u-boot@lists.denx.de

Kumar Gala wrote:
>>>From e76f97d16c5932d19d698e42c6376d6bbdca2ecf Mon Sep 17 00:00:00 2001
> From: Kumar Gala <galak@kernel.crashing.org>
> Date: Fri, 15 Feb 2008 03:34:36 -0600
> Subject: [PATCH] Add sub-commands to fdt
> 
> fdt header                          - Display header info
> fdt bootcpu <id>                    - Set boot cpuid
> fdt memory <addr> <size>            - Add/Update memory node
> fdt rsvmem print                    - Show current mem reserves
> fdt rsvmem add <addr> <size>        - Add a mem reserve
> fdt rsvmem delete <index>           - Delete a mem reserves
> 
> Signed-off-by: Kumar Gala <galak@kernel.crashing.org>

Applied to u-boot-fdt.  Thanks.

FWIIW, I found that fdt header when the fdt address (blob) is invalid 
crashes my board.  On the one hand, that's what you get from playing 
with sharp knives - I'm reluctant to inhibit the header printout if the 
blob is invalid, because that may be what I'm trying to find out.  On 
the other hand, I hate to crash a board when it can be avoided.

At this point, I'm inclined to validate the magic number (only) before 
doing the dump.

gvb