From: Adrian Hunter <ext-adrian.hunter@nokia.com>
To: Kyungmin Park <kmpark@infradead.org>
Cc: "linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>
Subject: Re: [RFC] [PATCH] [MTD] [OneNAND] Add write-while-program operation
Date: Mon, 18 Aug 2008 09:47:07 +0300 [thread overview]
Message-ID: <48A91AEB.2060503@nokia.com> (raw)
In-Reply-To: <9c9fda240808151825u2693ab3h3d7524e90a6d24af@mail.gmail.com>
Kyungmin Park wrote:
> Before comment the patch, I first wonder which mtd user can use this feature?
Well, UBI does large writes when it moves PEBs (for wear leveling or in response
to bit-flips), or for atomic LEB change, or when it updates volumes.
> To work correctly, the upper layer sends more than 2 pages write size.
> umm just override the write buffer in omap2. maybe assume mtdblock?
I am not sure what you mean here.
next prev parent reply other threads:[~2008-08-18 6:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-14 14:15 [RFC] [PATCH] [MTD] [OneNAND] Add write-while-program operation Adrian Hunter
2008-08-16 1:25 ` Kyungmin Park
2008-08-18 6:47 ` Adrian Hunter [this message]
2008-10-14 13:48 ` Adrian Hunter
2008-10-15 2:43 ` 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=48A91AEB.2060503@nokia.com \
--to=ext-adrian.hunter@nokia.com \
--cc=kmpark@infradead.org \
--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