From: Artem Bityutskiy <dedekind1@gmail.com>
To: Robert Jarzmik <robert.jarzmik@free.fr>
Cc: Mike Dunn <mikedunn@newsguy.com>,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
linux-mtd@lists.infradead.org,
Shmulik Ladkani <shmulik.ladkani@gmail.com>,
Brian Norris <computersforpeace@gmail.com>,
David Woodhouse <dwmw2@infradead.org>
Subject: Re: [PATCH] mtd: nand: Use the mirror BBT descriptor when reading its version
Date: Mon, 18 Jun 2012 23:28:16 +0300 [thread overview]
Message-ID: <1340051296.1971.5.camel@koala> (raw)
In-Reply-To: <87ehpc1oyb.fsf@free.fr>
[-- Attachment #1: Type: text/plain, Size: 921 bytes --]
On Mon, 2012-06-18 at 19:59 +0200, Robert Jarzmik wrote:
> To store worn out blocks, each filesystem implementation has to do something
> smart. UBI has it way, SAFTL (docg3 fs) has its way, etc ...
UBI does not do anything about storing the bad block table. UBI relies
on the MTD layer - it may mark a block as bad and MTD should take care
of storing this information either in the OOB or in the BBT on in both
places.
> But in the end, the bad block table is immutable, and represents factory bad
> blocks, not up-to-date list of bad blocks.
How do you store the information about the later developed bad blocks?
> As to whether you should kill it or not, it's up to the maintainer of diskonchip
> I suppose.
There is no DoC maintainer, you can consider yourself to be the
maintainer, because you and Mike are the only people who care about this
AFAICS.
--
Best Regards,
Artem Bityutskiy
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2012-06-18 20:28 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-10 10:58 [PATCH] mtd: nand: Use the mirror BBT descriptor when reading its version Shmulik Ladkani
2012-06-10 17:02 ` Sebastian Andrzej Siewior
2012-06-11 5:59 ` Brian Norris
2012-06-12 10:42 ` Artem Bityutskiy
2012-06-13 0:42 ` Brian Norris
2012-06-18 11:12 ` Artem Bityutskiy
2012-06-18 17:59 ` Robert Jarzmik
2012-06-18 20:28 ` Artem Bityutskiy [this message]
2012-06-19 1:51 ` Mike Dunn
2012-06-24 18:52 ` Robert Jarzmik
2012-06-25 19:40 ` Mike Dunn
2012-06-26 15:41 ` Artem Bityutskiy
2012-06-19 1:40 ` Mike Dunn
2012-06-18 11:32 ` Artem Bityutskiy
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=1340051296.1971.5.camel@koala \
--to=dedekind1@gmail.com \
--cc=bigeasy@linutronix.de \
--cc=computersforpeace@gmail.com \
--cc=dwmw2@infradead.org \
--cc=linux-mtd@lists.infradead.org \
--cc=mikedunn@newsguy.com \
--cc=robert.jarzmik@free.fr \
--cc=shmulik.ladkani@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.