From mboxrd@z Thu Jan  1 00:00:00 1970
From: Scott Wood <scottwood@freescale.com>
Date: Thu, 27 May 2010 14:10:22 -0500
Subject: [U-Boot] [PATCH] powerpc: add support for the Freescale P1022DS
 reference board
In-Reply-To: <4BFEC2FD.5050103@freescale.com>
References: <1274392909-16422-1-git-send-email-timur@freescale.com>
	<20100520223324.50594CCF026@gemini.denx.de>
	<4BFC1736.5030902@freescale.com>
	<20100526201014.97886EAC238@gemini.denx.de>
	<4BFD837D.2040508@freescale.com>
	<20100527070235.E8812EAC238@gemini.denx.de>
	<4BFE823A.1080409@freescale.com>
	<20100527181118.3C9F7EAC238@gemini.denx.de>
	<4BFEB922.9040106@freescale.com>
	<20100527190340.GA5915@schlenkerla.am.freescale.net>
	<4BFEC2FD.5050103@freescale.com>
Message-ID: <4BFEC39E.7040302@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

On 05/27/2010 02:07 PM, Timur Tabi wrote:
> Scott Wood wrote:
>
>> Passing the actual, known size of RAM (why guess when we know?) as "maxsize"
>> should eliminate the machine check problem[1] -- you'd just be using it as a
>> not particularly exhaustive memory tester.  I don't see why it should be
>> mandatory.
>
> The purpose of get_ram_size() is to verify the "known size of RAM".  That
> is, once you think you know how much RAM there is, you ask get_ram_size() to
> verify that claim.

It would still (sort of) verify that you don't have less than you claim. 
  Attempting to experimentally determine whether you have more than you 
claim is dangerous.

-Scott