From mboxrd@z Thu Jan  1 00:00:00 1970
From: Scott Wood <scottwood@freescale.com>
Date: Mon, 04 Aug 2008 15:55:37 -0500
Subject: [U-Boot-Users] [PATCH] fdt: add fdtcmd env var to allow post
 processing of device tree before boot
In-Reply-To: <F388F9D5-B685-4DD8-ACAC-146A46A1F04E@kernel.crashing.org>
References: <20080804202744.627D624885@gemini.denx.de>
	<F388F9D5-B685-4DD8-ACAC-146A46A1F04E@kernel.crashing.org>
Message-ID: <48976CC9.4030404@freescale.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:
> On Aug 4, 2008, at 3:27 PM, Wolfgang Denk wrote:
>> So just run the needed commands before you run "bootm" as part of your
>> boot command sequence.
> 
> This doesnt work.  Lets say I want to remove a node or property that  
> ft_board_setup() adds.  If I do what you are suggesting the node or  
> prop will get added back:
> 
> fdt addr <FOO>
> fdt boardsetup (we assume this adds /bar/prop)
> fdt rm /bar/prop
> bootm (will call ft_board_setup and add /bar/prop back)
> 
> This assumes I know the best location for the device tree before  
> "bootm" which I'd argue isn't really true.  Especially if my dtb is in  
> flash.

Why not?  Wouldn't it be just another environment variable, like the 
load address for the kernel?

-Scott