From mboxrd@z Thu Jan  1 00:00:00 1970
From: Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>
Date: Fri, 24 Apr 2009 23:47:17 +0200
Subject: [U-Boot] [PATCH 1/2] Fix OneNAND ipl to
	read	CONFIG_SYS_MONITOR_LEN
In-Reply-To: <20090424152118.GA27635@ld0162-tx32.am.freescale.net>
References: <22617689.32781240550892435.JavaMail.weblogic@epml08>
	<9c9fda240904232257o3caa5afeja62c6690b80d5b26@mail.gmail.com>
	<20090424152118.GA27635@ld0162-tx32.am.freescale.net>
Message-ID: <20090424214717.GB10032@game.jcrosoft.org>
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 10:21 Fri 24 Apr     , Scott Wood wrote:
> On Fri, Apr 24, 2009 at 02:57:52PM +0900, Kyungmin Park wrote:
> > Actually, I don't like the CONFIG_SYS_MONITOR_LEN approaches, now you
> > are consider the bad block at 1.
> > But we can also consider the bad block 2, if there two consecutive 2
> > bad block at block 1, 2, we should define the CONFIG_SYS_MONITOR_LEN
> > as 128KiB * 4 and reserved block block 4 always even though we use 2
> > blocks.
> 
> There are two separate constants -- the length of data excluding bad
> blocks, and the size of the region set aside for that data including bad
> blocks.  CONFIG_SYS_MONITOR_LEN is the former.
we may need to detect the u-boot.bin size dynamicly instead of staticly

as Scott NACK

Best Regards,
J.