public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: David Brown <mtd@davidb.org>
To: Nancy <nancydreaming@gmail.com>
Cc: linux-mtd@lists.infradead.org, kmpark@infradead.org
Subject: Re: Does UBI support MLC nand flash?
Date: Tue, 1 Jan 2008 23:13:06 -0800	[thread overview]
Message-ID: <20080102071306.GA10292@old.davidb.org> (raw)
In-Reply-To: <bae050c10801012219m71d7415du4379e5b5d5a54560@mail.gmail.com>

On Wed, Jan 02, 2008 at 02:19:16PM +0800, Nancy wrote:
>oh, forgot to metion UBI.
>UBI has two headers for each LED/PED, they are not write at same time.
>Is that against MLC nand's no ramdom write and  write only once
>permission?

Yes.  Perhaps one could be written at the beginning of the block and one
always written at the end of the block.  It wastes more pages that way,
though.

If the second write is only to indicate that the block is invalid, it
_might_ be permissible to write it out of order, since the out of order
write might only corrupt data.  Depending on underlying device
implementation, it might also just not work, though.

Dave

  reply	other threads:[~2008-01-02  7:16 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-02  1:42 Does UBI support MLC nand flash? Nancy
2008-01-02  4:45 ` Kyungmin Park
2008-01-02  6:13   ` Nancy
2008-01-02  6:19     ` Nancy
2008-01-02  7:13       ` David Brown [this message]
2008-01-02 12:39       ` Josh Boyer
2008-01-02 16:52         ` David Brown
2008-01-02 17:13           ` Josh Boyer
2008-01-02 17:17             ` David Brown
2008-01-03  7:19               ` Nancy
2008-01-02  7:11     ` David Brown
2008-01-02  7:23     ` Kyungmin Park
     [not found]       ` <bae050c10801020133h3b121b2ft47911a0d84921868@mail.gmail.com>
2008-01-02  9:36         ` Nancy
2008-01-02  9:37           ` Nancy
2008-01-02  7:27     ` David Brown
2008-01-02 13:46 ` Adrian Hunter

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=20080102071306.GA10292@old.davidb.org \
    --to=mtd@davidb.org \
    --cc=kmpark@infradead.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=nancydreaming@gmail.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