public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: manningc2@actrix.gen.nz, "Thayne Harbaugh" <tharbaugh@lnxi.com>,
	"Jörn Engel" <joern@wohnheim.fh-wedel.de>
Cc: linux-mtd@lists.infradead.org
Subject: Re: Fw: corrupt my NAND flash device
Date: Wed, 30 Apr 2003 00:04:21 +0200	[thread overview]
Message-ID: <200304300004.21495.tglx@linutronix.de> (raw)
In-Reply-To: <20030429194216.56C10447E@blood.actrix.co.nz>

On Tuesday 29 April 2003 21:37, Charles Manning wrote:
> > I have tested this with both chiptypes. The erase is aborted and
> > restarted by the erase function.
>
> A couple of comments:
> * "Both chip types" is misleading. There is not just a Toshiba and a
> Samsung chiptype. Each of these vendors provides chips with different
> internal architectures. That is one of the reason characteristics like the
> number of partial page writes etc change.

True. I meant a couple of different types.

> * "Aborted and restarted" is perhaps incorrect. Don't you really mean
> "aborted and re-performed"? I do not believe these parts have a way of
> remembering their internal eraseure state to restart line NOR parts do.

Yep. The command is thrown away according to datasheet and it is issued again 
later. Sorry for misleading expression.

> My other question remains: do you really gain anything by adding the erase
> interruption feature? From a Samsung datasheet:
> * Block erase takes typically 2ms, max 3ms.
> * If you do a reset while the part is erasing, the reset might take as long
> as 500us.
> You then have to restart the erase for it to take another 2ms (unless it
> gets interrupted again).

I have done test on different chips. The erasetime varies a lot. The peak was 
45ms. So that matters IMHO. The specs allow up to 200ms.

> This certainly adds some unpredictability to the behaviour. Most likely it
> does all work, but is it worth it?

Depends. :)

> > It would really be interresting, if those problems are in related to an
> > erase abort. Can anybody insert some debugging in nand_get_chip, where
> > the abort is done?
>
> Yes, it certianly would be interesting.

I think, I have to throw out some harsh remarks again to get an answer on this 
question, as the "hurray, I'm willing to volunteer" replies are not really 
much up to now. :)

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

  reply	other threads:[~2003-04-29 21:05 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-22 20:03 Fw: corrupt my NAND flash device Alex Samoutin
2003-04-22 20:26 ` Jörn Engel
2003-04-22 20:59   ` Jörn Engel
2003-04-23 20:45 ` Charles Manning
2003-04-24 18:25   ` Alex Samoutin
2003-04-25 13:01     ` Jörn Engel
2003-04-25 22:23       ` Alex Samoutin
2003-04-25 23:10         ` Thayne Harbaugh
2003-04-26 10:23           ` Jörn Engel
2003-04-28 15:02             ` Thayne Harbaugh
2003-04-28 21:14               ` Charles Manning
2003-04-28 22:59                 ` Thomas Gleixner
2003-04-29  1:23                   ` Charles Manning
2003-04-29  8:03                     ` Thomas Gleixner
2003-04-29 19:37                       ` Charles Manning
2003-04-29 22:04                         ` Thomas Gleixner [this message]
2003-04-30 16:54           ` Alex Samoutin
2003-04-30 18:13             ` Thomas Gleixner
2003-07-02 17:43               ` Alex Samoutin
2003-07-02 17:53                 ` Jasmine Strong
2003-07-02 20:10                   ` Alex Samoutin
2003-07-04  1:43                   ` David Woodhouse
2003-07-03  5:44                 ` Stephan Linke
2003-07-05 15:15                   ` Thomas Gleixner
2003-07-07  9:27                     ` Stephan Linke
2003-07-07 13:48                       ` Thomas Gleixner
2003-07-08  7:50                         ` David Woodhouse
2003-04-26 10:18         ` Jörn Engel
2003-04-28  8:57           ` Thomas Gleixner
  -- strict thread matches above, loose matches on Subject: below --
2003-08-18 11:36 Eugeny Mints
2003-04-22  7:05 Paul Wong

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=200304300004.21495.tglx@linutronix.de \
    --to=tglx@linutronix.de \
    --cc=joern@wohnheim.fh-wedel.de \
    --cc=linux-mtd@lists.infradead.org \
    --cc=manningc2@actrix.gen.nz \
    --cc=tharbaugh@lnxi.com \
    /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