From mboxrd@z Thu Jan  1 00:00:00 1970
From: Nishanth Menon <menon.nishanth@gmail.com>
Date: Mon, 16 Mar 2009 13:39:21 +0200
Subject: [U-Boot] U-boot and JFFS2
In-Reply-To: <19F8576C6E063C45BE387C64729E73940427C52509@dbde02.ent.ti.com>
References: <19F8576C6E063C45BE387C64729E73940427C52509@dbde02.ent.ti.com>
Message-ID: <49BE3A69.6000402@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:35 PM:
> Hi,
>
> On the OMAP3 EVM board, I have four partition on my Onenand flash of which /dev/mtd4 is a JFFS2 partition.
>
> After booting up linux, I use the following command to mount the jffs2 empty partition.
>
> Linux#> mount -t jffs2 /dev/mtdblock4 /mnt
>
> Then I do a reboot .
>
> When u-boot boots up it gives bad erase block for all the blocks used by /dev/mtd4.
>
> The reason is the JFFS2 filesystem is putting some signature at location 0x0 and 0x1 of OOB locations
> of every block.
>
> Is there a way this can be avoided ?
>
>   
A)
mount -t jffs2 /dev/mtdblock4 /mnt
umount /mnt
sync
reboot

this gives the garbage collector time to put the cleanmarkers in place.

B) is the kernel's oob layout and ECC strategy (h/w vs s/w ecc) same as
that used for u-boot?

Regards,
Nishanth Menon