linux-mtd.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Artem Bityutskiy <dedekind1@gmail.com>
To: angelo <angelo70@gmail.com>
Cc: "linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>
Subject: Re: erase block < 8KiB
Date: Fri, 14 Oct 2011 11:45:26 +0300	[thread overview]
Message-ID: <1318581933.12351.70.camel@sauron> (raw)
In-Reply-To: <4E8977DF.1030808@gmail.com>

On Mon, 2011-10-03 at 10:52 +0200, angelo wrote:
> Hi all,
> 
> i read several mail about this limitation.
> 
> http://lists.infradead.org/pipermail/linux-mtd/2011-February/033851.html
> http://lists.infradead.org/pipermail/linux-mtd/2011-June/036498.html
> 
> 
> I have a 4 KiB erase-size, common of some SST nor flash'es like mine 
> (SST 39VF3201B).
> 
>  From all the posts i read here in the list, there seems not to be any 
> solution guaranteed.
> 
> The tricky change to mkfs.jffs2 don't work for me. It seems to work for 
> small files, but i still get error messages copying a 600KB file in the 
> partition.
> If it's true that the minimal jffs2 block is 4KB + some bytes, of course 
> the patch to mkfs.jffs2 can't work.
> 
> Some one suggested the "virtual erase block" solution. I would like to 
> try to implement it, if i have the time.
> 
> In any case, for the common users, is there maybe another flash file 
> system that can work with 4KiB erase size ?

Just hack your driver and make it emulate larger eraseblocks and make
JFFS2 happy. Should not be difficult.

-- 
Best Regards,
Artem Bityutskiy

  parent reply	other threads:[~2011-10-14  8:45 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-03  8:52 erase block < 8KiB angelo
2011-10-06 12:47 ` Fabio Giovagnini
2011-10-14  8:45 ` Artem Bityutskiy [this message]
2011-10-14  8:50   ` angelo
2011-10-14  9:15     ` Artem Bityutskiy
2011-10-14  9:34       ` angelo
2011-12-16 12:59         ` Guillaume LECERF

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=1318581933.12351.70.camel@sauron \
    --to=dedekind1@gmail.com \
    --cc=angelo70@gmail.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;
as well as URLs for NNTP newsgroup(s).