From: "Alex Samoutin" <samoutin@hotbox.ru>
To: <linux-mtd@lists.infradead.org>
Subject: Re: NAND subsector writing problem
Date: Thu, 30 Jan 2003 18:11:23 -0800 [thread overview]
Message-ID: <004701c2c8ce$107caea0$1a00a8c0@itc.intrinsyc.com> (raw)
In-Reply-To: 20030130210325.0F2BB405E@tiger.actrix.co.nz
don't know much about sub-page writing. I've only took latest MTD snapshot
and wrote hardware level driver for NAND chip on IBM 405ep board. And then
started "nandtest" program from the same snapshot. So, if "mixing ECC and
sub-page writes is
invalid" then something wrong in "nand.c" or "nandtest.o"
And furthermore - that was not ECC error, it was error during verify read
after write (read and write buffer not match).
Also I have troubles with JFFS2 :(. nand_write_page failed after verify
( If CONFIG_MTD_NAND_VERIFY_WRITE not defined - I have no error message)
Alex.
----- Original Message -----
From: "Charles Manning" <manningc2@actrix.gen.nz>
To: "Alex Samoutin" <samoutin@hotbox.ru>; <linux-mtd@lists.infradead.org>
Sent: Thursday, January 30, 2003 12:57 PM
Subject: Re: NAND subsector writing problem
> There is no problem using this for JFFS2 or YAFFS since neither use
> sub-page writes.
>
> ECC applies to the whole page. Thus, mixing ECC and sub-page writes is
> invalid.
>
> -- Charles
>
next prev parent reply other threads:[~2003-01-31 1:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-30 1:10 NAND subsector writing problem Alex Samoutin
2003-01-30 8:23 ` David Woodhouse
2003-01-30 20:57 ` Charles Manning
2003-01-31 2:11 ` Alex Samoutin [this message]
2003-01-31 4:01 ` Charles Manning
2003-01-31 7:10 ` Thomas Gleixner
2003-02-01 2:10 ` Alex Samoutin
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='004701c2c8ce$107caea0$1a00a8c0@itc.intrinsyc.com' \
--to=samoutin@hotbox.ru \
--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