From: Thomas Gleixner <tglx@linutronix.de>
To: Alice Hennessy <ahennessy@mvista.com>
Cc: Steve Tsai <startec@ms11.hinet.net>,
'David Woodhouse' <dwmw2@infradead.org>,
Linux MTD mailing list <linux-mtd@lists.infradead.org>
Subject: Re: NAND Configuration
Date: Thu, 08 Aug 2002 10:59:23 +0200 [thread overview]
Message-ID: <1028797164.9592.2.camel@thomas.tec.linutronix.de> (raw)
In-Reply-To: <3D518D06.B809B67@mvista.com>
On Wed, 2002-08-07 at 23:11, Alice Hennessy wrote:
> > Have you ever erased your flash with erase /dev/mtdX ?
> > This may have caused the problem, because erase is not aware of bad
> > block handling and may have erased a block, which was marked as bad
> > already and erased the bad block marker too. So if you write to this
> > block, you get a write failure and therefor a read failure afterwards.
> > I will change nand.c, so that bad blocks cannot be erased anymore.
> >
>
> >From looking at nand_erase(), it appears that the attempted erase of a bad
> block would
> result in not performing the erase and exiting with -EIO, correct?
>
> What is the preferred method to erase nand?
>
> Alice
With actual code in CVS you can use erase(all) /dev/mtdX. I modified it,
that attempts to erase bad block's are rejeceted in any case. The
previous version let you erase bad blocks, if CONFIG_NAND_ECC_JFFS2 was
not set. But now it's forced by default.
--
Thomas
____________________________________________________
linutronix - competence in embedded & realtime linux
http://www.linutronix.de
mail: tglx@linutronix.de
next prev parent reply other threads:[~2002-08-08 8:59 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-06 7:25 NAND Configuration Steve Tsai
2002-08-06 9:07 ` Thomas Gleixner
2002-08-06 10:40 ` Steve Tsai
2002-08-06 12:16 ` Thomas Gleixner
2002-08-07 9:08 ` Steve Tsai
2002-08-07 10:05 ` David Woodhouse
2002-08-07 10:19 ` Steve Tsai
2002-08-07 10:49 ` Thomas Gleixner
2002-08-07 21:11 ` Alice Hennessy
2002-08-08 8:59 ` Thomas Gleixner [this message]
2002-08-08 9:14 ` David Woodhouse
2002-08-08 9:28 ` Thomas Gleixner
2002-08-08 2:47 ` Steve Tsai
2002-08-08 5:23 ` Steve Tsai
2002-08-08 9:11 ` Thomas Gleixner
2002-08-08 9:37 ` Steve Tsai
2002-08-08 11:05 ` David Woodhouse
2002-08-09 6:53 ` Steve Tsai
2002-08-09 8:09 ` Thomas Gleixner
2002-08-10 7:54 ` Steve Tsai
2002-08-10 8:41 ` Thomas Gleixner
2002-08-12 6:30 ` Steve Tsai
2002-08-06 9:45 ` Thomas Gleixner
2002-08-06 10:25 ` Steve Tsai
2002-08-06 12:28 ` Thomas Gleixner
2002-08-06 12:32 ` David Woodhouse
2002-08-06 12:40 ` Thomas Gleixner
2002-08-07 10:45 ` Steve Tsai
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1028797164.9592.2.camel@thomas.tec.linutronix.de \
--to=tglx@linutronix.de \
--cc=ahennessy@mvista.com \
--cc=dwmw2@infradead.org \
--cc=linux-mtd@lists.infradead.org \
--cc=startec@ms11.hinet.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox