public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: timwu@interepoch.com.tw (Tim Wu)
To: linux-mtd@lists.infradead.org
Subject: not enough blocks for JFFS?
Date: Mon, 24 Mar 2003 10:31:01 +0800	[thread overview]
Message-ID: <3E7E6DE5.5000003@interepoch.com.tw> (raw)

Hi! Everybody:

The system I'm working on use a 4MB NOR flash.
The block size of the 4MB flash is 64KB.
It also has eight smaller(8KB) blocks at bottom.
Since, on this system, I don't have much data to write(less than 10KB),
a CRAMFS(readonly)+JFFS(writable) combination should be pretty good for me.

Here comes the problem.  The bootloader has occupied the first three 8KB 
blocks.  I have only five 8K blocks available for JFFS.  It always fails 
when I overwrite an existed file on the JFFS partition.

I've checked the mailing list archive.  It seems JFFS/JFFS2 needs at 
least five blocks to work and the number '5' is adjustable.  Could 
somebody tell me where I can modify in JFFS source to have it run on 
fewer blocks?

Thanks.

             reply	other threads:[~2003-03-24  2:31 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-24  2:31 Tim Wu [this message]
2003-03-24 22:17 ` not enough blocks for JFFS? Russ Dill
2003-03-25  0:05   ` Jörn Engel
2003-03-25  2:13     ` Tim Wu
2003-03-25  2:21       ` Russ Dill
2003-03-25 11:24         ` Tim Wu
2003-03-25 12:33         ` Jörn Engel
2003-03-25 19:06           ` Russ Dill
2003-03-26 13:04             ` Jörn Engel
2003-03-25 12:51     ` David Woodhouse
2003-03-25 13:33       ` Jörn Engel
2003-03-25 14:36         ` David Woodhouse
2003-03-26 13:27           ` Jörn Engel
2003-03-30 19:01           ` Jörn Engel
2003-03-30 19:07             ` Jörn Engel
2003-03-30 19:23             ` David Woodhouse
2003-03-30 20:08               ` Jörn Engel
2003-04-07 13:16                 ` 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=3E7E6DE5.5000003@interepoch.com.tw \
    --to=timwu@interepoch.com.tw \
    --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