From mboxrd@z Thu Jan  1 00:00:00 1970
From: Nishanth Menon <menon.nishanth@gmail.com>
Date: Mon, 16 Mar 2009 13:44:46 +0200
Subject: [U-Boot] U-boot and JFFS2
In-Reply-To: <19F8576C6E063C45BE387C64729E73940427C52513@dbde02.ent.ti.com>
References: <19F8576C6E063C45BE387C64729E73940427C52509@dbde02.ent.ti.com>
	<49BE3A69.6000402@gmail.com>
	<19F8576C6E063C45BE387C64729E73940427C52513@dbde02.ent.ti.com>
Message-ID: <49BE3BAE.1080505@gmail.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

Pillai, Manikandan said the following on 03/16/2009 01:41 PM:
> The cleanmarkers are being written in location 0x0 and 0x1 of the OOB space
> And they are the problem since when u-boot comes up it does a scan and decided
> That since these OOB locations do not contain 0xff, the blocks are bad.
>   
offset 0 and 1 in a x16 large page micron device is reserved for
badblock marker - u-boot is checking the correct location and if those
locations dont have 0xff, it is noted as bad blocks. if cleanmarker is
being written there, you'd need to fix the kernel board file etc..
Regards,
Nishanth Menon