public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Vitaly Wool <vwool@ru.mvista.com>
Cc: M Sudharshana-A18475 <sudharshana@motorola.com>,
	linux-mtd@lists.infradead.org
Subject: Re: Nand read/write
Date: Thu, 13 Jul 2006 11:58:34 +0200	[thread overview]
Message-ID: <87bqrt967p.wl%tglx@linutronix.de> (raw)
In-Reply-To: <44B616F0.3050409@ru.mvista.com>

At Thu, 13 Jul 2006 13:48:32 +0400,
Vitaly Wool wrote:
> 
> M Sudharshana-A18475 wrote:
> > It is a flash partition where no file system is defined for that
> > mount-able partition. Read/write operations are performed on /dev/mtd0
> > (place where memory partition is mounted
> Ok, then the answer is yes, unless your board driver selects 
> NAND_ECC_NONE for ECC calculation.
> 
> I'd also expect to hear a lection on top-posting if I were you.

And you get a lesson for the wrong answer. :)

The question was if bad blocks are handled when he accesses
the FLASH via /dev/mtdX. The answer is:

It's not possible to write / erase bad blocks.

But there is no bad block replacement functionality when you
access the FLASH through the raw MTD interface. Neither MTD
nor NAND provide anything like this. Raw access has to take
care of this itself. Therefor we require that images are
written with nandwrite instead of dd or cp. nandwrite has
the simplest form of bad block handling (skip it).

	tglx

  reply	other threads:[~2006-07-13  9:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <B7803DC652E2F9458758AEBB6A5FD60FF88DB0@ZMY16EXM67.ds.mot.com>
2006-07-13  9:48 ` Nand read/write Vitaly Wool
2006-07-13  9:58   ` Thomas Gleixner [this message]
2006-07-13  9:14 M Sudharshana-A18475
2006-07-13  9:19 ` Vitaly Wool
2006-07-17 10:32 ` dedekind

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=87bqrt967p.wl%tglx@linutronix.de \
    --to=tglx@linutronix.de \
    --cc=linux-mtd@lists.infradead.org \
    --cc=sudharshana@motorola.com \
    --cc=vwool@ru.mvista.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox