public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Chuck Meade <chuckmeade@mindspring.com>
To: linux-mtd@lists.infradead.org,
	"Chuck Meade (mindspring)" <chuckmeade@mindspring.com>
Subject: jffs2 eraseblock size, and actual flash device eraseblock size
Date: Tue, 03 Jul 2007 02:47:39 -0400	[thread overview]
Message-ID: <4689F10B.9040401@mindspring.com> (raw)

Hello,

I am generating a jffs2 image for a target that can have one of two
different flash devices installed.  One of these flash devices has
an eraseblock size of 0x20000 bytes, and one has an eraseblock size of
0x10000 bytes.  The storage size of the flash devices is the same.
It would be nice to be able to use the same jffs2 image on both target
flash variants.

I have read what I could find related to this, including the FAQ, such
as here:  http://www.linux-mtd.infradead.org/doc/jffs2.html
which states "creating an image with smaller eraseblock size than the
actual hardware is harmless -- it just gives annoying messages".

I would like to get your expert opinions on what would be the _best_
approach here.  The possible approaches are to create an image with the
eraseblock set to 0x10000, or to 0x20000.  The 0x10000 size would be
smaller than the actual flash eraseblock size on the flash device with
actual eraseblock size=0x20000.  And the opposite problem occurs if you
create an image with eraseblock 0x20000 -- it is larger than the actual
erase block size when using the flash device with eraseblock size 0x10000.

What are the pros and cons here, with respect to efficiency?  Would
both of the above choices even work?

Thanks,
Chuck

             reply	other threads:[~2007-07-03  6:48 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-03  6:47 Chuck Meade [this message]
2007-07-11 18:55 ` jffs2 eraseblock size, and actual flash device eraseblock size Chuck Meade
2007-07-11 20:08   ` Jörn Engel

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=4689F10B.9040401@mindspring.com \
    --to=chuckmeade@mindspring.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