From: "David Byron" <dbyron@hheld.com>
To: <linux-mtd@lists.infradead.org>
Subject: nandwrite in FAQ
Date: Tue, 1 Aug 2006 13:59:57 -0700 [thread overview]
Message-ID: <001001c6b5ad$727d9400$c834800a@RudiDell> (raw)
[-- Attachment #1: Type: text/plain, Size: 210 bytes --]
Related to
http://lists.infradead.org/pipermail/linux-mtd/2006-July/016184.html, what
do you think of removing the -j argument to nandwrite in the NAND FAQ?
Definitely would have saved me a bunch of time.
-DB
[-- Attachment #2: nand.xml.patch --]
[-- Type: application/octet-stream, Size: 624 bytes --]
diff --git a/faq/nand.xml b/faq/nand.xml
index f208d44..1a39c46 100644
--- a/faq/nand.xml
+++ b/faq/nand.xml
@@ -43,7 +43,7 @@ is also neccecary before you copy a fs-i
<p>Yes, as long as your chip does not contain bad blocks. Make sure, that the erasesize you set to mkfs.jffs2
is the same as the erasesize of your chip. Data will only be written with ECC, if your default settings for
oob-layout selection are set for JFFS2. For bad block aware copying, use nandwrite from mtd-utils.<br />
-nandwrite -j /dev/mtdX image
+nandwrite /dev/mtdX image
</p>
<h3>Can I use seek/read/write on /dev/mtdX ?</h3>
next reply other threads:[~2006-08-01 20:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-01 20:59 David Byron [this message]
2006-08-02 4:47 ` nandwrite in FAQ Artem B. Bityutskiy
-- strict thread matches above, loose matches on Subject: below --
2006-08-02 14:42 David Byron
2006-08-02 14:44 ` Artem B. Bityutskiy
2006-08-02 14:52 ` Artem B. Bityutskiy
2006-08-02 14:59 David Byron
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='001001c6b5ad$727d9400$c834800a@RudiDell' \
--to=dbyron@hheld.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