All of lore.kernel.org
 help / color / mirror / Atom feed
From: Artem Bityutskiy <dedekind1@gmail.com>
To: Ricard Wanderlof <ricard.wanderlof@axis.com>
Cc: liulunzuo <liulunzuo@gmail.com>,
	"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>
Subject: Re: Dose linux-mtd really support mlc nand flash?
Date: Mon, 25 Jan 2010 11:56:13 +0200	[thread overview]
Message-ID: <1264413373.2549.28.camel@localhost> (raw)
In-Reply-To: <Pine.LNX.4.64.1001250947000.32263@lnxricardw.se.axis.com>

On Mon, 2010-01-25 at 09:53 +0100, Ricard Wanderlof wrote:
> On Sat, 23 Jan 2010, liulunzuo wrote:
> 
> >  Mlc nand flash should be write only once per write operation(NOP=1),
> >  but i found when i use mtd-utils to write a mtdchar device with oob ,
> >  it write a page twice: page and oob zone wrote separately,
> >  and mtdchar.c support no way to write a page and oob zone to the mlc
> > nand flash at the same time.
> 
> As far as I understand, mtd has not been used very much with MLC flash. 
> There are some thoughts about using UBI on MLC 
> (http://www.linux-mtd.infradead.org/faq/ubifs.html#L_why_ubiformat) but it 
> seems it hasn't been tested to any extent. At any rate, UBI does not use 
> the spare area in the flash for itself (like jffs2 does with cleanmarkers 
> in empty blocks. Don't know how yaffs goes about its stuff).

Yeah, a little better links for the MLC thoughts, though:

http://www.linux-mtd.infradead.org/faq/ubi.html#L_mlc
http://www.linux-mtd.infradead.org/faq/ubifs.html#L_ubifs_mlc

-- 
Best Regards,
Artem Bityutskiy (Артём Битюцкий)

      reply	other threads:[~2010-01-25  9:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-23  9:51 Dose linux-mtd really support mlc nand flash? liulunzuo
2010-01-25  8:53 ` Ricard Wanderlof
2010-01-25  9:56   ` Artem Bityutskiy [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=1264413373.2549.28.camel@localhost \
    --to=dedekind1@gmail.com \
    --cc=linux-mtd@lists.infradead.org \
    --cc=liulunzuo@gmail.com \
    --cc=ricard.wanderlof@axis.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.