From: Ivan Djelic <ivan.djelic@parrot.com>
To: Wolfram Sang <w.sang@pengutronix.de>
Cc: "Koen Beel" <koen.beel.barco@gmail.com>,
"Huang Shijie" <b32955@freescale.com>,
"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
"Shawn Guo" <shawn.guo@linaro.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"Lothar Waßmann" <LW@KARO-electronics.de>
Subject: Re: GPMI-NAND Status?
Date: Sun, 14 Aug 2011 10:11:39 +0200 [thread overview]
Message-ID: <20110814081139.GD17063@parrot.com> (raw)
In-Reply-To: <20110805135133.GA26981@pengutronix.de>
On Fri, Aug 05, 2011 at 02:51:33PM +0100, Wolfram Sang wrote:
(...)
>
> problem overwriting all-0xff data in NAND [2]
> =============================================
>
> Although it occured only when writing JFFS2 images so far, this is a generic
> issue and needs to be fixed, right?
>
>
(...)
> [2] http://lists.infradead.org/pipermail/linux-mtd/2011-July/037104.html
As explained in the thread linked above, this issue should be fixed in your
flashing tool, _not_ in your driver. The nand device you are using does not
support programming pages multiple times in a row; pretending it does in the
special all-0xff case is inefficient (you need to detect all-0xff data) and
unnecessary (just do not program blank pages !).
BR,
Ivan
next prev parent reply other threads:[~2011-08-14 8:11 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-05 13:51 GPMI-NAND Status? Wolfram Sang
2011-08-08 6:21 ` Huang Shijie
2011-08-08 9:19 ` Koen Beel
2011-08-08 10:37 ` Huang Shijie
2011-08-08 12:42 ` Koen Beel
2011-08-09 6:36 ` Huang Shijie
2011-08-09 7:58 ` Koen Beel
2011-08-09 8:18 ` Huang Shijie
2011-08-09 8:25 ` Koen Beel
2011-08-09 5:11 ` Huang Shijie
2011-08-09 6:25 ` Koen Beel
2011-08-09 6:40 ` Huang Shijie
2011-08-09 9:45 ` Wolfram Sang
2011-08-09 9:35 ` Wolfram Sang
2011-08-09 10:54 ` Huang Shijie
2011-08-09 20:42 ` Wolfram Sang
2011-08-08 9:12 ` Huang Shijie
2011-08-09 9:19 ` Wolfram Sang
2011-08-09 10:41 ` Huang Shijie
2011-08-09 11:36 ` Lothar Waßmann
2011-08-14 8:11 ` Ivan Djelic [this message]
2011-08-14 18:31 ` Wolfram Sang
2011-08-15 5:41 ` Lothar Waßmann
2011-08-15 6:30 ` Lin Tony-B19295
2011-08-15 8:41 ` Ivan Djelic
2011-08-15 8:29 ` Ivan Djelic
2011-08-15 9:31 ` Lothar Waßmann
2011-08-15 12:54 ` Ivan Djelic
2011-08-15 13:37 ` Lothar Waßmann
2011-08-15 16:34 ` Artem Bityutskiy
2011-08-15 16:18 ` Artem Bityutskiy
2011-08-15 16:22 ` Artem Bityutskiy
2011-08-15 16:57 ` Ivan Djelic
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=20110814081139.GD17063@parrot.com \
--to=ivan.djelic@parrot.com \
--cc=LW@KARO-electronics.de \
--cc=b32955@freescale.com \
--cc=koen.beel.barco@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-mtd@lists.infradead.org \
--cc=shawn.guo@linaro.org \
--cc=w.sang@pengutronix.de \
/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