From: Philip Rakity <prakity@yahoo.com>
To: linux-mtd@lists.infradead.org
Subject: setting PAD parameter with JFFS2 and NAND -- what is correct thing to do ?
Date: Tue, 2 Dec 2008 09:23:05 -0800 (PST) [thread overview]
Message-ID: <461019.6371.qm@web58901.mail.re1.yahoo.com> (raw)
I am trying to understand what value to set the pad parameter to when making a JFFS2 image (including using sumtool) for NAND flash.
The NAND flash has 2KiB sectors, 256KiB erase size, and is 2GB.
I use flase_eraseall -j when erasing the flash and the flash HAS bad blocks.
The image size is less than the 2GB size of the flash.
I have tried both specifying pad (rounded up) to the erase block size and omitting pad. When I write to the NAND there are recovered CRC errors from time to time as well as the other "errors" indicated in the FAQ.
If could set pad to the SIZE of the NAND flash, but because of bad blocks I am not sure this is correct...
Guidance Please.
Philip
next reply other threads:[~2008-12-02 17:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-02 17:23 Philip Rakity [this message]
2008-12-03 16:44 ` setting PAD parameter with JFFS2 and NAND -- what is correct thing to do ? Grant Erickson
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=461019.6371.qm@web58901.mail.re1.yahoo.com \
--to=prakity@yahoo.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