From: "Jörn Engel" <joern@wohnheim.fh-wedel.de>
To: Steven Scholz <steven.scholz@imc-berlin.de>
Cc: MTD <linux-mtd@lists.infradead.org>
Subject: Re: JFFS2 uncompressed?
Date: Tue, 8 Apr 2003 17:56:37 +0200 [thread overview]
Message-ID: <20030408155637.GA5065@wohnheim.fh-wedel.de> (raw)
In-Reply-To: <3E92E57A.5000900@imc-berlin.de>
On Tue, 8 April 2003 17:06:34 +0200, Steven Scholz wrote:
>
> It's working! :o)
The good thing about clean code is that it's so easy to add ugly code
on top of it. :)
> Would you like a define like
>
> #define USE_COMPRESSION
>
> or rather
>
> #define DONT_USE_COMP
> or something like that!?
The change is simple enough already, no neef for more #ifdefs.
There is currently ongoing discussion about implementing conditional
compression in several places. Either per compile, as you did it, per
mount point or per inode.
Per inode is the most flexible, was already prepared a long time ago
and is imo the way. If/when this is done, the only reason to use your
simpler approach is to shrink the kernel image.
In short: don't bother.
> BTW: Where could I put it so mkfs.jffs2 will find it?
> Or should we add a command line option to mkfs.jffs2?
I'd prefer a command line option.
Jörn
--
The grand essentials of happiness are: something to do, something to
love, and something to hope for.
-- Allan K. Chalmers
next prev parent reply other threads:[~2003-04-08 15:56 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-08 13:59 JFFS2 uncompressed? Steven Scholz
2003-04-08 14:19 ` Jörn Engel
2003-04-08 14:33 ` Steven Scholz
2003-04-08 15:03 ` Jörn Engel
2003-04-08 15:06 ` Steven Scholz
2003-04-08 15:56 ` Jörn Engel [this message]
2003-04-08 15:43 ` Steven Scholz
2003-04-08 16:00 ` Jörn Engel
2003-04-08 16:05 ` Steven Scholz
2003-04-08 16:08 ` David Woodhouse
2003-04-08 16:30 ` Thayne Harbaugh
2003-04-08 16:33 ` David Woodhouse
2003-04-11 6:44 ` Steven Scholz
2003-04-08 15:46 ` Steven Scholz
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=20030408155637.GA5065@wohnheim.fh-wedel.de \
--to=joern@wohnheim.fh-wedel.de \
--cc=linux-mtd@lists.infradead.org \
--cc=steven.scholz@imc-berlin.de \
/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