From mboxrd@z Thu Jan  1 00:00:00 1970
From: Jerry Van Baren <gerald.vanbaren@smiths-aerospace.com>
Date: Fri, 18 May 2007 12:30:07 -0400
Subject: [U-Boot-Users] Ideas on U-Boot configuration with FDT
In-Reply-To: <464DD073.1030709@freescale.com>
References: <464D6D4A.4000200@grandegger.com> <464DB7C1.4050509@freescale.com>
	<464DC663.90707@smiths-aerospace.com>
	<464DC7D8.2050703@freescale.com>
	<464DCEAE.3030201@smiths-aerospace.com>
	<464DD073.1030709@freescale.com>
Message-ID: <464DD48F.8070808@smiths-aerospace.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

Timur Tabi wrote:
> Jerry Van Baren wrote:
> 
>> Yes, that is what "fdt addr" does today, it tells the u-boot innards 
>> where the blob is (sets/changes the blob location).  The user can 
>> download a new blob and switch to using it via the "fdt addr" command.
> 
> By "change", I thought you meant that "fdt addr" would actually move the 
> device tree, since that's technically changing the address.  Perhaps you 
> meant "set the address"?

Yes.

>> The user can use the "fdt addr" command to set/change the location of 
>> the blob.  Moving blobs is not out of scope, it is what "fdt move" does. 
> 
> How is "fdt move" different than cp.b followed by another "fdt addr"?

Conceptually the same thing but easier: you don't have to know (guess) 
the blob size because fdt_open_into() gets the size from the source blob.

gvb