From mboxrd@z Thu Jan  1 00:00:00 1970
From: Scott Wood <scottwood@freescale.com>
Date: Fri, 16 May 2008 15:43:59 -0500
Subject: [U-Boot-Users] [PATCH] Fix NAND erase progress error
In-Reply-To: <42848A5C5A0D1E47B026E644DD49B08E026D1A27@mail>
References: <1210963157-7727-1-git-send-email-hugo.villeneuve@lyrtech.com>
	<20080516194054.GB2795@loki.buserror.net>
	<42848A5C5A0D1E47B026E644DD49B08E026D1A19@mail>
	<482DEC17.5060607@freescale.com>
	<42848A5C5A0D1E47B026E644DD49B08E026D1A23@mail>
	<482DEFB8.6050704@freescale.com>
	<42848A5C5A0D1E47B026E644DD49B08E026D1A27@mail>
Message-ID: <482DF20F.6030902@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

Hugo Villeneuve wrote:
> Scott Wood wrote:
>> Hugo Villeneuve wrote:
>>> I would be perfectly happy if the mtd driver reported a warning when
>>> the requested erase size is not an exact multiple of the block size,
>>> and allow the whole block erase to proceed. Then my patch would make
>>> sense. 
>> That's what the mtd-2.6.22.1 branch in the NAND repository does.  I
>> think it should reject such requests, though.
> 
> I don?t like that behavior. Let?s say that I want to program a new
> binary application of 2.8MB. I want to be able to simply erase 2.8MB,
> without having to do fancy math computations on my calculator based
> on the block size :)

Hmm... maybe a flag to request round-up?  Or at the very least, have 
"help nand" mention the rounding-up behavior.

-Scott