Table) for
some particular blocks (Ex:10, 11)
Updating status is, first clear status, second set bad block status.
Patrick's patch is only fixed the issue for setting status process,
so this patch fix the clearing status process.
Signed-off-by: Yoshio Furuyama
---
drivers/mtd/nand/bbt.c |
From: "Doyle, Patrick"
In the unlikely event that both blocks 10 and 11 are marked as bad (on a
32 bit machine), then the process of marking block 10 as bad stomps on
cached entry for block 11. There are (of course) other examples.
Signed-off-by: Patrick Doyle
Reviewed-by: Richard Weinberger
Doyle, Patrick (1):
Fix corner case in bad block table handling.
Yoshio Furuyama (1):
Fix the issue for clearing status process
drivers/mtd/nand/bbt.c | 6 --
1 file changed, 4 insertions(+), 2 deletions(-)
--
2.25.1
>From Yoshio Furuyama # This line is ignored.
From: Yoshio Furuyama
Subject:
In-Reply-To:
Fixed issue of manages BBT (Bad Block Table).
It didn't mark correctly when a specific block was bad block.
This issue occurs when the bad block mark (3-bit chunk) is
crosses over 32 bit (e.g. Block10, Block21...) unit.
Signed-off-by: Yoshio Furuyama
---
drivers/mtd/nand/bbt.c | 6
Add device table for Toshiba Memory products.
Also, generalize OOB layout structure and function names.
Signed-off-by: Yoshio Furuyama
---
drivers/mtd/nand/spi/toshiba.c | 79 +---
1 file changed, 65 insertions(+), 14 deletions(-)
diff --git a/drivers/mtd
6 matches
Mail list logo