On Tue, 2004-12-07 at 09:25 +1100, Aras Vaichas wrote:
> Thomas Gleixner wrote:
> > On Mon, 2004-12-06 at 02:25, Aras Vaichas wrote:
> >>Is there a utility that writes to every single page, reads back the data and
> >>then marks the pages correctly?
> > No.
> >>Or are those "bad eraseblocks" permanently lost?
> > You can hack nand_base.c to allow the erasing of the blocks which are
> > marked bad.
>
> Yes, I eventually realised that nand_base.c was stopping me from erasing the
> badly marked blocks which means that there is no way to force the chip to erase
> those blocks. I guess that this is a policy issue considering that it would be
> unusual to create so many bad blocks except during development (like happened
> to me).
>
> What I am hoping now is that the write-verify code in YAFFS will rediscover
> which blocks are actually bad and mark them as such.
>
> e.g. in the YAFFS makefile, I keep this commented out
> #IGNORE_WRITE_VERIFY = -DCONFIG_YAFFS_DISBLE_WRITE_VERIFY
Get rid of the command function in your driver first.
tglx
(text/plain)