From mboxrd@z Thu Jan  1 00:00:00 1970
From: Timur Tabi <timur@freescale.com>
Date: Fri, 18 May 2007 10:01:28 -0500
Subject: [U-Boot-Users] Ideas on U-Boot configuration with FDT
In-Reply-To: <464DBFDD.6030209@grandegger.com>
References: <464D6D4A.4000200@grandegger.com> <464DB7C1.4050509@freescale.com>
	<464DBBB2.1060006@grandegger.com> <464DBCB4.3050409@freescale.com>
	<464DBFDD.6030209@grandegger.com>
Message-ID: <464DBFC8.4050708@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

Wolfgang Grandegger wrote:

> RAM is _not_ available at that stage.

Do we really need RAM to parse the device tree and configure U-Boot?  I think not.

The device tree has a memory section:

	memory {
		device_type = "memory";
		reg = <00000000 10000000>;	// 256MB
	};

So the question is: do we want U-Boot to use this node to determine how much RAM there is, 
or do we want U-Boot to determine how much RAM there is and update this node?

> Depends, you might be right for FLASH on a 32-bit bus. On slow ROM 
> devices and slow processors, it matters.

I still don't see how it's important.  If the device tree is on slow memory, so what?  You 
have to read it sooner or later.  If your board can't handle this feature, then don't 
enable it, and configure U-Boot the "old fashioned way".

-- 
Timur Tabi
Linux Kernel Developer @ Freescale