public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Steve Tsai <startec@ms11.hinet.net>
Cc: 'David Woodhouse' <dwmw2@infradead.org>,
	Linux MTD mailing list <linux-mtd@lists.infradead.org>
Subject: RE: NAND Configuration
Date: Wed, 07 Aug 2002 12:49:05 +0200	[thread overview]
Message-ID: <1028717345.19447.249.camel@thomas.tec.linutronix.de> (raw)
In-Reply-To: <002f01c23dfb$dea583f0$5501a8c0@synso.com.tw>

On Wed, 2002-08-07 at 12:19, Steve Tsai wrote:
> > > JFFS2 on NOR type flash does not use buffering, OOB check and bad 
> > > block management, but it can be used now. I meant that 
> > > CONFIG_JFFS2_FS_NAND is not defined, maybe the driver still 
> > can work, 
> > > but it is not good as the original one.
> > 
> > JFFS2 cannot work on NAND flash without the extra code enabled by 
> > CONFIG_JFFS2_FS_NAND. You need to batch writes into 
> > page-sized chunks and 
> > use ECC. It looks like you have enabled CONFIG_JFFS2_FS_NAND 
> > in the log you 
> > show -- is that correct?
> > 
> 
> Yes, I enable CONFIG_JFFS2_FS_NAND. I follow
> http://www.linux-mtd.infradead.org/tech/nand.html to config the
> settings. Can I do not care ECC on NAND flash?
> 
ECC _HAS_ to be enabled !

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.

Another problem could be your command delay time. You have set it to
15µsec. Is that correct for your chip ? Which chip are you using ?
Have you tried to set it to a higher value ? 

-- 
Thomas 
____________________________________________________
linutronix - competence in embedded & realtime linux
http://www.linutronix.de
mail: tglx@linutronix.de

  reply	other threads:[~2002-08-07 10:49 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 [this message]
2002-08-07 21:11               ` Alice Hennessy
2002-08-08  8:59                 ` Thomas Gleixner
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=1028717345.19447.249.camel@thomas.tec.linutronix.de \
    --to=tglx@linutronix.de \
    --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