From: Michael Lawnick <nospam_lawnick@gmx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] JFFS2-Summary support for u-boot
Date: Mon, 29 Sep 2008 08:45:15 +0000 (UTC) [thread overview]
Message-ID: <loom.20080929T083848-425@post.gmane.org> (raw)
Hi *,
please feel free to correct me if I tell sh**:
As far as I was told, bad JFFS2 boot performance of u-boot is result of not
supporting summary. (Because there is no JFFS2 but only JFFS support?)
So my question:
Has anybody done or is planning in next time (~weeks) to add summary support for
u-boot JFFS2? We need a file system on 32MB NOR flash with wear leveling and
acceptable boot time. Ubi is currently not supported for NOR, JFFS2 slow, ... :-(
TIA
Kind Regards,
M.Lawnick
next reply other threads:[~2008-09-29 8:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-29 8:45 Michael Lawnick [this message]
2008-09-29 9:34 ` [U-Boot] JFFS2-Summary support for u-boot Joakim Tjernlund
2008-09-29 11:34 ` Michael Lawnick
2008-09-29 11:54 ` Joakim Tjernlund
2008-09-29 12:49 ` Michael Lawnick
2008-09-29 14:02 ` Joakim Tjernlund
2008-09-30 7:40 ` Michael Lawnick
2008-10-07 1:23 ` Detlev Zundel
2008-09-29 14:05 ` Detlev Zundel
2008-09-29 18:13 ` Michael Lawnick
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=loom.20080929T083848-425@post.gmane.org \
--to=nospam_lawnick@gmx.de \
--cc=u-boot@lists.denx.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