From mboxrd@z Thu Jan  1 00:00:00 1970
From: Wolfgang Denk <wd@denx.de>
Date: Tue, 14 Aug 2007 09:06:25 +0200
Subject: [U-Boot-Users] [PATCH] Fix initrd/dtb interaction
In-Reply-To: Your message of "Mon, 13 Aug 2007 23:05:42 EDT."
	<46C11C06.8060106@gmail.com>
Message-ID: <20070814070625.99D5D24041@gemini.denx.de>
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

In message <46C11C06.8060106@gmail.com> you wrote:
>
> > Second, I asked you before to implement this similar like the  initrd
> > location  can  be  controlled  using  the  "initrd_high"  environment
> > variable (see my message Tue, 07 Aug 2007 21:21:19 +0200). AFAICT you
> > never replied to this.
> 
> I believe Andy got this from me.  I keyed off his statement that "The 
> blob must be within CFG_BOOTMAPSZ..." so I suggested he compare 
> of_flat_tree to CFG_BOOTMAPSZ, since that was the criteria that he stated.
> 
> <http://comments.gmane.org/gmane.comp.boot-loaders.u-boot/30616>
> 
> I'm ignorant of the particulars, but I assumed from the above referenced 
> discussion/description that CFG_BOOTMAPSZ is a better criteria than 
> initrd_high.  True?  False?

I don't think it's better.  CFG_BOOTMAPSZ  is  a  hard  coded  limit.
initrd_high  (or fdt_high or whatever you will call it) allows you to
use the same value as default, but  overwrite  it  on  systems  which
don't  need  it  or have additional restrictions, i. e. it giveds you
added flexibility. This is IMHO a Good Thing (TM).

Best regards,

Wolfgang Denk

-- 
DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
If a man had a child who'd gone  anti-social,  killed  perhaps,  he'd
still tend to protect that child.
	-- McCoy, "The Ultimate Computer", stardate 4731.3