From: Dzuy Nguyen <dzuy@infinity-studios.com>
To: "linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>
Subject: Re: jffs2: Too few erase blocks (1)
Date: Mon, 09 Feb 2009 22:16:05 -0600 [thread overview]
Message-ID: <4990FF85.70709@infinity-studios.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0902091731030.22663@lnxricardw.se.axis.com>
I think I'll just use ext2. ext2 doesn't mind small partition. Writing
to it
should work the same as dd.
Ricard Wanderlof wrote:
> On Mon, 9 Feb 2009, Dzuy Nguyen wrote:
>
>
>> Thanks, Ricard. I didn't realize that jffs2 is not suitable for a small
>> partition. Yes,
>> 64K is all I can afford. I suppose I can dd the file, but doesn't that
>> provide no wear
>> leveling feature that jffs2 does?
>>
>
> No. But with one eraseblock you can't get much wear levelling anyway.
>
> It might not be too difficult to write an application that appends
> new data to existing data to the partition, erasing the whole block when
> it fills up and write the latest. Then you need something that will search
> for the latest version of the file. Something that jffs2 does, but on a
> smaller scale, acceptable for your application.
>
> /Ricard
> --
> Ricard Wolf Wanderlöf ricardw(at)axis.com
> Axis Communications AB, Lund, Sweden www.axis.com
> Phone +46 46 272 2016 Fax +46 46 13 61 30
>
> ______________________________________________________
> Linux MTD discussion mailing list
> http://lists.infradead.org/mailman/listinfo/linux-mtd/
>
next prev parent reply other threads:[~2009-02-10 4:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-09 5:52 jffs2: Too few erase blocks (1) Dzuy Nguyen
2009-02-09 8:50 ` Ricard Wanderlof
2009-02-09 15:39 ` Dzuy Nguyen
2009-02-09 16:32 ` Ricard Wanderlof
2009-02-10 4:16 ` Dzuy Nguyen [this message]
2009-02-10 12:41 ` Jamie Lokier
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=4990FF85.70709@infinity-studios.com \
--to=dzuy@infinity-studios.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