Bug 16639
| Summary: | All blocks of an older NAND device reported bad | ||
|---|---|---|---|
| Product: | Drivers | Reporter: | Janusz Krzysztofik (jkrzyszt) |
| Component: | Flash/Memory Technology Devices | Assignee: | David Woodhouse (dwmw2) |
| Status: | CLOSED CODE_FIX | ||
| Severity: | normal | CC: | rjw |
| Priority: | P1 | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Kernel Version: | 2.6.36-rc1 | Subsystem: | |
| Regression: | Yes | Bisected commit-id: | |
| Bug Depends on: | |||
| Bug Blocks: | 16444 | ||
Yes, this patch corrects the problem for me, thanks. And sorry for not checking your repository before reporting. Thanks, Janusz I think I have to come clean and admit that although the gitweb interface says it was committed 31 hours ago, I actually forgot to *push* it until just before I made comment #1 :) Thanks for the confirmation -- this will go to Linus in the next day or so. I think I have everything I need to submit in the tree now. Fixed by commit 065a1ed8de85583888b3d4f22c64b534a1fbdaaa . |
Latest changes to drivers/mtd/nand/nand-{base,bbt}.c break support for the following device found on my ARM OMAP based Amstrad Delta videophone: NAND device: Manufacturer ID: 0x98, Chip ID: 0x75 (Toshiba NAND 32MiB 3,3V 8-bit) All blocks are detected bad, resulting in the device being not usable at all. The problem has been introduced with the following commit: mtd: nand: refactor BB marker detection c7b28e25cb9beb943aead770ff14551b55fa8c79 Reverting it, plus two more that depend on it, corrects the problem for me. Since I'm new to NAND, please give me a hint how I could try to correct it other than reverting the commits, which I assume may be required by other, new devices. Thanks, Janusz