From: Russ.Dill@asu.edu (Russ Dill)
To: linux-mtd@lists.infradead.org
Subject: not enough blocks for JFFS?
Date: 24 Mar 2003 19:21:47 -0700 [thread overview]
Message-ID: <1048558906.2922.5.camel@gobbles> (raw)
In-Reply-To: <3E7FBB35.1050100@interepoch.com.tw>
On Mon, 2003-03-24 at 19:13, Tim Wu wrote:
> J?rn:
> Thanks for your quick patch. I will test it.
>
> JFFS2 without compression?
> What does it different from JFFS?
>
> No compression is OK for me. That's why I chose JFFS instead of JFFS2.
> Can the idea "with less reserved blocks" apply to JFFS?
> I prefer JFFS because JFFS2 is much larger than JFFS in code size, which
> makes
> I have to enlarge my flash partition for kernel.
Your goals would be better served by a user-space solution from what I
can tell. Not only would there be less code, but that code would be
compressed in cramfs. I'm able to use 1 boot block for blob, another for
static configuration, and the remaining two for configuration data saved
in this way.
next prev parent reply other threads:[~2003-03-25 2:21 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-24 2:31 not enough blocks for JFFS? Tim Wu
2003-03-24 22:17 ` Russ Dill
2003-03-25 0:05 ` Jörn Engel
2003-03-25 2:13 ` Tim Wu
2003-03-25 2:21 ` Russ Dill [this message]
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=1048558906.2922.5.camel@gobbles \
--to=russ.dill@asu.edu \
--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