public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: "dedekind" <dedekind@yandex.ru>
To: sudharshana@motorola.com
Cc: linux-mtd@lists.infradead.org
Subject: Re: Nand read/write
Date: Mon, 17 Jul 2006 14:32:02 +0400 (MSD)	[thread overview]
Message-ID: <44BB6722.000003.20811@mfront7.yandex.ru> (raw)
In-Reply-To: <B7803DC652E2F9458758AEBB6A5FD60FF88D90@ZMY16EXM67.ds.mot.com>

>I have the following scenario on an embedded Linux application.
>
>There is a partition in the NAND flash memory (with RAW type, no file
>system), which will be mounted and used for read/write. As an
>application which performs "read"/"write" on this partition after
>mounting, should it be assumed that "bad block algorithm" is covered? Or
>application has to handle the same?

Nope. But UBI can do a lot. Try to look at it.

  parent reply	other threads:[~2006-07-17 10:32 UTC|newest]

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

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=44BB6722.000003.20811@mfront7.yandex.ru \
    --to=dedekind@yandex.ru \
    --cc=linux-mtd@lists.infradead.org \
    --cc=sudharshana@motorola.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