From: "Joakim Tjernlund" <joakim.tjernlund@transmode.se>
To: <linux-mtd@lists.infradead.org>
Subject: Different erase block sizes in a JFFS2 partion.
Date: Thu, 28 Sep 2006 23:55:17 +0200 [thread overview]
Message-ID: <01de01c6e348$c94e7330$1267a8c0@Jocke> (raw)
Got multiple NOR chips with top and bottom boot blocks with diffrent EB size
then the rest of the blocks.
I want to put a JFFS2 FS spanning over several chips which makes the FS
cross top/bottom boot blocks.
Since(last I looked) JFFS2 can't deal with diffrent EB sizes on the same
partition I need do something about it.
I want to use point()/unpoint() and a cached memory mapping for burst access
and I don't know how to do that yet and I would like some ideas.
One idea I have is to reserve the boot blocks with a new type of JFFS2
node(similar to JFFS2_FEATURE_ROCOMPAT) that spans the whole boot block.
JFFS2 should not try to move or delete nodes of this type. Not sure
if thats a good idea or if its hard to impl. yet.
Better ideas anyone?
next reply other threads:[~2006-09-28 21:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-28 21:55 Joakim Tjernlund [this message]
2006-09-28 23:07 ` Different erase block sizes in a JFFS2 partion Josh Boyer
2006-09-29 6:43 ` Joakim Tjernlund
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='01de01c6e348$c94e7330$1267a8c0@Jocke' \
--to=joakim.tjernlund@transmode.se \
--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