From: Bill Gatliff <bgat@billgatliff•com>
To: Laurent Lagrange <lagrange@fr•oleane.com>
Cc: linuxppc-embedded@ozlabs•org
Subject: Re: Linux 2.6.x, MTD drivers and NAND flashes
Date: Mon, 11 Jun 2007 10:59:37 -0500 [thread overview]
Message-ID: <466D7169.1000407@billgatliff.com> (raw)
In-Reply-To: <000001c7ac3c$15e7da80$5201a8c0@GEG2400>
[-- Attachment #1: Type: text/plain, Size: 1384 bytes --]
Laurent Lagrange wrote:
> Hello,
>
> I use a Linux 2.6.9 on a 85xx custom board with a NAND flash.
>
> This flash has some bad blocks.
> NAND device: Manufacturer ID: 0xec, Chip ID: 0xf1 (Samsung NAND 128MiB
> 3,3V 8-bit)
> Scanning device for bad blocks
> Bad eraseblock 8 at 0x00100000
> Bad eraseblock 430 at 0x035c0000
> ...
> Creating 1 MTD partitions on "NAND 128MiB 3,3V 8-bit":
> 0x00000000-0x08000000 : "flash partition 1".
>
> I have selected in the kernel :
> 1) the MTD character and block supports for NAND,
> 2) the CRAMFS and JFFS2 supports for NAND.
>
> I can erase the flash but receive IO errors for each bad blocks (that
> seems right).
> I can mount an empty JFFS2 partition on the NAND and untar some
> directories and files in it.
>
> I would like to generate some JFFS2 images and program them in the
> flash with a character
> command like "cat img > /dev/mtd/0". If I dont encounter a bad block,
> it runs right else the
> command fails.
>
> This is a little bit annoying. So my question is simple :
> Is there a MTD character driver which can detect and ignore the bad
> blocks in a NAND flash ?
Wrong question. :)
With NAND, working directly with the media is indeed a pain because of
bad blocks. What's done instead is to leave that to the filesystem.
Pick a NAND-aware one like YAFFS.
b.g.
--
Bill Gatliff
bgat@billgatliff•com
[-- Attachment #2: Type: text/html, Size: 2835 bytes --]
next prev parent reply other threads:[~2007-06-11 16:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-11 15:20 Linux 2.6.x, MTD drivers and NAND flashes Laurent Lagrange
2007-06-11 15:59 ` Bill Gatliff [this message]
2007-06-11 19:59 ` Gary Kenaley
2007-06-12 10:06 ` Laurent Lagrange
2007-06-12 13:37 ` Detlev Zundel
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=466D7169.1000407@billgatliff.com \
--to=bgat@billgatliff$(echo .)com \
--cc=lagrange@fr$(echo .)oleane.com \
--cc=linuxppc-embedded@ozlabs$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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