From: Artem Bityutskiy <dedekind1@gmail.com>
To: Brian Norris <computersforpeace@gmail.com>
Cc: David Woodhouse <dwmw2@infradead.org>,
linux-mtd@lists.infradead.org,
Mike Frysinger <vapier.adi@gmail.com>,
Matthew Creech <mlcreech@gmail.com>
Subject: Re: 'nandwrite -o' on MLC NAND
Date: Mon, 15 Aug 2011 18:48:46 +0300 [thread overview]
Message-ID: <1313423331.8691.11.camel@sauron> (raw)
In-Reply-To: <CAN8TOE8VHm2jMkFonfi+4bvmP8ORVVdXA0vb3-X8+XCGfTuAaw@mail.gmail.com>
On Tue, 2011-08-02 at 12:01 -0700, Brian Norris wrote:
> Hi,
>
> For a while, I've been having problems with using `nandwrite -o' on
> MLC NAND flash. Nandwrite is never able to write the combined data+OOB
> properly and instead leaves the flash filled with junk. This is,
> apparently, because `nandwrite -o' writes to the flash twice, once for
> the page data and once for the OOB data. This is not allowed on MLC
> NAND, which allow only single writes.
>
> This is a problem with the user interface to the kernel as well as
> with nandwrite itself, since there is no interface that nandwrite can
> use to write data+OOB to flash in a single write. As I see it, we need
> to do three things:
>
> 1) Support a (new?) ioctl that handles writing data+oob in one go. I'm
> not sure if an existing interface can be extended or if this actually
> has to be a new one...
> 2) Update nandwrite (i.e., update the libmtd routines in mtd-utils) to
> utilize the new interface when possible.
> 3) Ensure that the raw/no-ECC options for nandwrite are operational
> with the new interface (i.e., `nandwrite -r')
I guess making the old interfaces to be based on the new one internally
is also needed to keep things clean. Then we can declare the old
interfaces "legacy and obsolete", but will have to support anyway, of
course.
--
Best Regards,
Artem Bityutskiy
next prev parent reply other threads:[~2011-08-15 15:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-02 19:01 'nandwrite -o' on MLC NAND Brian Norris
2011-08-15 15:48 ` Artem Bityutskiy [this message]
2011-08-16 1:51 ` Brian Norris
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=1313423331.8691.11.camel@sauron \
--to=dedekind1@gmail.com \
--cc=computersforpeace@gmail.com \
--cc=dwmw2@infradead.org \
--cc=linux-mtd@lists.infradead.org \
--cc=mlcreech@gmail.com \
--cc=vapier.adi@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