From mboxrd@z Thu Jan  1 00:00:00 1970
From: Martin Egholm Nielsen <martin@egholm-nielsen.dk>
Date: Wed, 16 Feb 2005 08:35:12 +0100
Subject: [U-Boot-Users] Re: JFFS2 images written from U-Boot unusable   in Linux? (Round
 2)
In-Reply-To: <41E5183D.1020604@intracom.gr>
References: <crlq3v$t6e$1@sea.gmane.org> <69A56150-6260-11D9-BA9B-000A95A5473A@gumstix.com> <29B9DA05-6264-11D9-AB91-000A95B312BA@onz.com> <crtfkb$6k4$1@sea.gmane.org> <crunro$316$1@sea.gmane.org> <41E5183D.1020604@intracom.gr>
Message-ID: <cuusuk$ifd$1@sea.gmane.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

>> New information entered the scene: I tried another (identical) board 
>> today having none of the "Bad eraseblock" messages from my Linux 
>> kernel. And then everything worked!
>> Hence, my boardsupplier suggested that U-Boot "ignored" these "Bad 
>> eraseblock" that the NAND presumable was born with... What do you think?
=== 8< 8< 8< ===
Pantelis Antoniou wrote:
> NAND support is currently broken when bad blocks are present.
> Will sent patches shortly dealing with the problems...
Has these been submitted yet?

BR,
  Martin Egholm