Andre,
On Monday 17 September 2007 16:32, Andre Renaud wrote:
> We were having some issues with a ~4 month old yaffs checkout,
> where it would incorrectly think that blocks were bad. It
> appeared as though it was using MTD_OOB_AUTO to read the OOB
> tags, but then assuming that byte 5 of these contained the bad
> block marker. This was all before the large patch which added
> yaffs_mtdif1.c. Has anyone seen this issue in older versions -
> was it a known bug?
More details needed... MTD version, versions of the
yaffs_mtd*.c files (see $Id in files, or use 'ident' command).
I presume you have a small page device -- it has the bad-block
marker at the 6th byte (so offset 5) of oob/space on the chip.
What is your MTD nand_oobinfo definition? -- see MTD's
nand_base.c source file, or perhaps your platform NAND mapping
code.
Do you know if your build of yaffs_mtd.c is using the
translate_spare2oob() calls? -- depends on kernel version
seen during Yaffs build.
-imcd
(text/plain)