All of lore.kernel.org
 help / color / mirror / Atom feed
From: K Richard Pixley <rpixley@graphitesystems.com>
To: linux-mtd@lists.infradead.org
Subject: jffs2 usage question: nandwrite
Date: Thu, 06 Nov 2014 18:47:43 -0800	[thread overview]
Message-ID: <545C32CF.9060502@graphitesystems.com> (raw)

I'm a newbie to flash file systems and I've spent my day reading. 
However, I seem to be missing something.

Several sets of instructions encourage me to build my file system using 
mkfs.jffs2, which I understand creates an image, (akin to mkisofs), 
rather than operating on a device file.  However, once I have the image, 
they recommend placing the image onto flash using nandwrite.

I can't find any doc on nandwrite, but I'm guessing that it does a "bad 
block aware" sequential copy, meaning that it simply skips any blocks 
that it recognizes as bad according to a manufacturer mark. Assuming so, 
doesn't this hole in my fresh jffs2 file system cause jffs2 grief?  I 
mean, it would cause most other file systems grief to have an extra 
block inserted in the middle of their block sequence.

What am I missing?

--rich

             reply	other threads:[~2014-11-07  2:48 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-07  2:47 K Richard Pixley [this message]
2014-11-07  5:35 ` jffs2 usage question: nandwrite Iwo Mergler
2014-11-07  8:38   ` Ricard Wanderlof

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=545C32CF.9060502@graphitesystems.com \
    --to=rpixley@graphitesystems.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.