[PATCH] mtd: nand: Use the mirror BBT descriptor when reading its version
Artem Bityutskiy
dedekind1 at gmail.com
Mon Jun 18 16:28:16 EDT 2012
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
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: This is a digitally signed message part
URL: <http://lists.infradead.org/pipermail/linux-mtd/attachments/20120618/5cef9cec/attachment.sig>
More information about the linux-mtd
mailing list