public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: "Jörn Engel" <joern@logfs.org>
To: Kyungmin Park <kyungmin.park@samsung.com>
Cc: dwmw2@infradead.org, linux-mtd@lists.infradead.org
Subject: Re: [RFC][PATCH][JFFS2] JFFS2 doesn't use OOB at MLC NAND/OneNAND
Date: Wed, 5 Dec 2007 02:03:18 +0100	[thread overview]
Message-ID: <20071205010318.GG26112@lazybastard.org> (raw)
In-Reply-To: <20071205005553.GA28782@party>

On Wed, 5 December 2007 09:55:53 +0900, Kyungmin Park wrote:
> 
> It's the preparation patch for the MLC NAND/OneNAND flash.
> The current jffs2 implementation at NAND case uses the NOP 2, cleanmarker and data each page 0. It breaks the NOP 1 limitation in MLC flash.
> 
> With this patch, we don't write the cleanmarker at oob area.
> I'm not sure it should use the cleanmarker at data area as NOR does.
> Apart from the cleanmarker, there's serious POR issue, paired page at MLC.
> 
> The paired page problem is that if the some page is broken, the paired page is also broken even though it is written correctly at previous time.
> That's the reason the cleanmarker is not big issue at this time.
> 
> Now we support the NOP 1 and later we have to address this paired page issue. I'm not sure when this problem is addressed.
> 
> Any comments are welcome.

I like it.

Jörn

-- 
Joern's library part 3:
http://inst.eecs.berkeley.edu/~cs152/fa05/handouts/clark-test.pdf

      reply	other threads:[~2007-12-05  1:08 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-05  0:55 [RFC][PATCH][JFFS2] JFFS2 doesn't use OOB at MLC NAND/OneNAND Kyungmin Park
2007-12-05  1:03 ` Jörn Engel [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=20071205010318.GG26112@lazybastard.org \
    --to=joern@logfs.org \
    --cc=dwmw2@infradead.org \
    --cc=kyungmin.park@samsung.com \
    --cc=linux-mtd@lists.infradead.org \
    /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