From mboxrd@z Thu Jan  1 00:00:00 1970
From: Hollis Blanchard <hollis_blanchard@mentor.com>
Date: Tue, 07 Dec 2010 10:40:40 -0800
Subject: [U-Boot] [PATCH] Honor /memory/reg node in DTB files
In-Reply-To: <20101207065234.DC3BB280@gemini.denx.de>
References: <4CFD863A.7070000@mentor.com>
	<20101207065234.DC3BB280@gemini.denx.de>
Message-ID: <4CFE7FA8.2030701@mentor.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

On 12/06/2010 10:52 PM, Wolfgang Denk wrote:
> If you define that the device tree is the "master" for information
> about the memory layout (and potentially other hardware specifics),
> then you should be consequent and pass make U-Boot process this
> information.  We've discussed before that there are a number of cases
> where it would be nice if U-Boot itself could be configured usign a
> device tree.  This appears to be another one.
I *think* what you're suggesting is basically providing u-boot with a 
single device tree, even when it will load multiple operating systems. 
The tree would then look something like this:

/
     cpus
         ...
     memory
         reg = <0 20000000>
     soc
         ...
     partitions
         partition at 0
             memory
                 reg = <0 10000000>
         partition at 1
             memory
                 reg = <10000000 10000000>

U-boot would then be responsible for constructing multiple device trees 
(one for each partition) itself, based on the additional information 
found in the "partitions" node.

Is that correct?

Hollis Blanchard
Mentor Graphics, Embedded Systems Division