public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Adrian Hunter <ext-adrian.hunter@nokia.com>
To: ext Nancy <nancydreaming@gmail.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: Does UBI support MLC nand flash?
Date: Wed, 02 Jan 2008 15:46:29 +0200	[thread overview]
Message-ID: <477B95B5.2030509@nokia.com> (raw)
In-Reply-To: <bae050c10801011742s762cd289ta9aae5881e294598@mail.gmail.com>

ext Nancy wrote:
> Sir / Madam,
> 
>              Does UBI support MLC nand flash?
> 
>              According to the MLC nand spec, It is only allowed write
> once per erased
> block, moreover, it isn't allowed ramdom write during a block, means
> the page number must be increase during the write PED operation.
> 
> 
> --
> Best Regards,
> Nancy
> 
> ______________________________________________________
> Linux MTD discussion mailing list
> http://lists.infradead.org/mailman/listinfo/linux-mtd/

As Artem is on holiday, I am replying to this.

UBI (and UBIFS) write sequentially to NAND pages within an eraseblock so there should be no problem with MLC NAND.

However the driver must not set up subpages because UBI will prefer to write subpages if they are available.

      parent reply	other threads:[~2008-01-02 13:54 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
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 [this message]

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=477B95B5.2030509@nokia.com \
    --to=ext-adrian.hunter@nokia.com \
    --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