From: Thomas Gleixner <tglx@linutronix.de>
To: pgrayson@realmsys.com
Cc: linux-mtd@lists.infradead.org
Subject: Re: Can you really write a jffs2 image with nandwrite?
Date: Tue, 01 Mar 2005 20:16:10 +0100 [thread overview]
Message-ID: <1109704571.8540.26.camel@tglx.tec.linutronix.de> (raw)
In-Reply-To: <1109700711.5043.53.camel@pgrayson1.realmsys.com>
On Tue, 2005-03-01 at 11:11 -0700, Peter Grayson wrote:
> > nandwrite does not expect oob data for jffs2 images.
>
> But it appears nandwrite can accept oob data. It does have the --oob
> option and when this option is set nandwrite reads the oob data from the
> image and does an ioctl() to the mtd character device to write it.
Yes it can, but JFFS2 images contain no oob data
> With mkfs.jffs2, I had some confusion about the pagesize option. I was
> thinking that it corresponded to the NAND pagesize, but that is not
> correct, it sets the jffs2 filesystem page size.
Oops, missed that one.
> With nandwrite, the -j option causes things to not work. This was a
> great stumbling block for me. It proved to be critical to _not_ use the
> -j (or -o) option with nandwrite. This is in direct conflict with
> instructions in the FAQ.
Could you please correct the FAQ and add the steps you took and send a
patch ?
tglx
next prev parent reply other threads:[~2005-03-01 19:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-01 2:14 Can you really write a jffs2 image with nandwrite? Peter Grayson
2005-03-01 2:47 ` Thomas Gleixner
2005-03-01 18:11 ` Peter Grayson
2005-03-01 19:16 ` Thomas Gleixner [this message]
2005-03-01 20:47 ` Peter Grayson
2005-03-02 9:57 ` Artem B. Bityuckiy
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=1109704571.8540.26.camel@tglx.tec.linutronix.de \
--to=tglx@linutronix.de \
--cc=linux-mtd@lists.infradead.org \
--cc=pgrayson@realmsys.com \
/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