public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: David Woodhouse <dwmw2@infradead.org>
To: Dvir Oren <dviro@lucidvon.com>
Cc: mtd@infradead.org
Subject: Re: Bad Block Table
Date: Tue, 28 Mar 2000 10:37:40 +0100	[thread overview]
Message-ID: <17860.954236260@devel2.axiom.internal> (raw)
In-Reply-To: <38E076C2.534F661E@lucidvon.com>


dviro@lucidvon.com said:
>  1.  Where is it located?  Oron from M-Systems said that before erase
> the flash it is important to save it.  So where is it located, and how
> can I save it? (Will dd work?) 

Stored in the same erase block as the NFTL Media Header(s). 
Look for BadUnitTable in util/nftl_format.c


dviro@lucidvon.com said:
>  2.  Also mentioned was that during the lifetime of the flash, if a
> new bad block is found, it is marked as a bad block.  This will be
> effective only before doing a boot.  Question is, who is responsible
> for finding those bad blocks - the M-Systems kernel driver?

This is effective only until you next reboot - i.e. it's not written to the 
BadUnitTable, only stored in memory. Presumably, the M-Systems driver notices 
a failure when it tries to erase or write a block, and marks it bad.


dviro@lucidvon.com said:
>  3.  And if the driver is responsible for this, does the MTD driver do
> the same? 

Not yet.



--
dwmw2




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

  reply	other threads:[~2000-03-28  9:37 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-03-28  9:09 Bad Block Table Dvir Oren
2000-03-28  9:37 ` David Woodhouse [this message]
2000-03-28 11:44   ` Dvir Oren
2000-03-28 11:59   ` Dvir Oren
2000-03-28 12:52     ` David Woodhouse
  -- strict thread matches above, loose matches on Subject: below --
2000-04-04 14:55 Dvir Oren
2000-03-26 14:21 Dvir Oren

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=17860.954236260@devel2.axiom.internal \
    --to=dwmw2@infradead.org \
    --cc=dviro@lucidvon.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