public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Kyle Harris <kharris@nexus-tech.net>
To: Oron Ogdan <Orono@m-sys.com>
Cc: MTD <mtd@infradead.org>
Subject: Re: Questions about MTD
Date: Mon, 20 Mar 2000 21:59:15 -0500	[thread overview]
Message-ID: <38D6E583.3C2E1334@nexus-tech.net> (raw)
In-Reply-To: B17893052A17D211A9860060978F7E63014A0544@mail.msys.co.il



Oron Ogdan wrote:
> 
> Kyle Harris Wrote:
> > So will the device still work if the static table has been deleted?
> >
> Yes and no, Yes after you format it again the bad block table will be empty,
> So all blocks (including the originally bad ones will be used) which will
> work 99.99% of the time. But No I would not go to manufacturing with such
> devices. It can only be used for R&D and even this is pretty risky.
> 

I don't mean to drag this on.... but I'd really like to understand this.
How are the original bad blocks determined (if they work 99.99% of the
time). Are they the bad blocks indicated by the virgin flash device
(e.g., Samsung indicates bad blocks by writing zero data to the first
page)? Or are they determined by some testing process? I'm guessing the
0.01% failure would be such that data is not retained, since if the
block fails on a write/verify it will simply be mapped as bad and
skipped.

Thanks for any additional info, Kyle.


To unsubscribe, send "unsubscribe mtd" to majordomo@infradead.org

  reply	other threads:[~2000-03-21  3:01 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-03-20 20:51 Questions about MTD Oron Ogdan
2000-03-21  2:59 ` Kyle Harris [this message]
  -- strict thread matches above, loose matches on Subject: below --
2000-03-21 12:36 Oron Ogdan
2000-03-20 20:51 Oron Ogdan
2000-03-20 19:34 Dvir Oren
2000-03-21  9:01 ` David Woodhouse
2000-03-20 14:11 Oron Ogdan
2000-03-20 16:17 ` Kyle Harris
2000-03-20 11:17 Oron Ogdan
2000-03-20 13:51 ` Kyle Harris
2000-03-18 20:05 Dvir Oren
2000-03-20  9:41 ` David Woodhouse
2000-03-20 18:06 ` Bill Roman
2000-03-20 18:49   ` David Woodhouse

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=38D6E583.3C2E1334@nexus-tech.net \
    --to=kharris@nexus-tech.net \
    --cc=Orono@m-sys.com \
    --cc=mtd@infradead.org \
    /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