From: "Ajay Jain" <ajain@neomagic.com>
To: <linux-mtd@lists.infradead.org>
Subject: Nand Flash write fails
Date: Fri, 22 Sep 2006 21:09:20 +0530 [thread overview]
Message-ID: <04c001c6de5d$46f73a10$561fa8c0@pcajain> (raw)
Hi,
I have set up a JFFS2 partition on my NAND flash. The board driver in
question is my own. I can successfully 'mkfs' & 'mount' that partition.
However when I start copying any file to it, it gives the following
error.
nand_write_ecc: vectored attempt to write not page aligned data: to =
20b9e4, total_len = 44
Write of 68 bytes at 0x0000b9e4 failed. returned -22, retlen 0
Not marking the space at 0x0000b9e4 as dirty because the flash driver
returned retlen zero
I was looking up the code of the mtd nand layer. I see that in case the
data is not alligned on the page boundary, it returns back giving this
error. Therefore my question is that is it the responsibility of the
"jffs2 layer" or "mtd" layer to issue writes that are aligned to page
boundary.
ANY suggestions are welcome.
Thanks.
next reply other threads:[~2006-09-22 15:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-22 15:39 Ajay Jain [this message]
2006-09-28 0:20 ` Nand Flash write fails Thomas Gleixner
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='04c001c6de5d$46f73a10$561fa8c0@pcajain' \
--to=ajain@neomagic.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