From: David Woodhouse <dwmw2@infradead.org>
To: Kyungmin Park <kmpark@infradead.org>
Cc: Kyungmin Park <kyungmin.park@samsung.com>, linux-mtd@lists.infradead.org
Subject: Re: [PATCH] [MTD][OneNAND] Multi Level Chip (MLC) OneNAND support
Date: Wed, 23 Apr 2008 02:33:30 +0100 [thread overview]
Message-ID: <1208914410.9212.714.camel@pmac.infradead.org> (raw)
In-Reply-To: <9c9fda240804221749u4c235a3fv54926f8acfd2e605@mail.gmail.com>
On Wed, 2008-04-23 at 09:49 +0900, Kyungmin Park wrote:
> On Wed, Apr 23, 2008 at 12:06 AM, David Woodhouse <dwmw2@infradead.org> wrote:
> > On Thu, 2008-01-03 at 09:03 +0900, Kyungmin Park wrote:
> > > This patch enables the MLC OneNAND support
> > > Now it's basic support. We need to work more.
> > >
> > > In MLC, we use the 4KiB BufferRam instead of 2KiB.
> > > With this reason it is changed to read/write data from/to BufferRAM 0 and
> > > we can't use read-while-load.
> > >
> > > It passed the nand-tests module and it diffed against the OneNAND MTD tree instead of MTD one.
> >
> > Did you intend this to be merged?
> >
>
> Yes, Before merge this one
> Another patch should be merged first.
>
> "[JFFS2] JFFS2 doesn't use OOB at MLC NAND/OneNAND"
> http://patchwork.ozlabs.org/linux-mtd/patch?id=16536
Hm, yeah... that was the other thing I wanted to ask you about.
I'm really not wonderfully happy with it. Have we done any powerfail
testing with MLC chips?
Maybe it would be better to just refuse to mount, until/unless we have a
proper solution?
--
dwmw2
next prev parent reply other threads:[~2008-04-23 1:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-03 0:03 [PATCH] [MTD][OneNAND] Multi Level Chip (MLC) OneNAND support Kyungmin Park
2008-01-03 6:20 ` [PATCH] [MTD][OneNAND] Multi Level Cell " Kyungmin Park
2008-04-22 15:06 ` [PATCH] [MTD][OneNAND] Multi Level Chip " David Woodhouse
2008-04-23 0:49 ` Kyungmin Park
2008-04-23 1:33 ` David Woodhouse [this message]
2008-04-23 2:16 ` Kyungmin Park
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=1208914410.9212.714.camel@pmac.infradead.org \
--to=dwmw2@infradead.org \
--cc=kmpark@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