From: Martin Egholm Nielsen <martin@egholm-nielsen.dk>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] JFFS2+U-Boot writing an image that has been "SUMMARY"-patched?
Date: Wed, 06 Apr 2005 16:26:35 +0200 [thread overview]
Message-ID: <d30rer$mft$1@sea.gmane.org> (raw)
Hi there,
I'm considering patching my Linux kernel JFFS2 code with the "summary"
patch:
http://www.inf.u-szeged.hu/jffs2/mount.php
decreasing mount time severely. In short, this patch requires modifying
some data in the end of each eraseblock - also in the image that should
be written.
However, I'm planning on using u-boot to write the Linux root-fs - using
"nand write.jffs2" - and was wondering whether this function
(write.jffs2) actually cared about what it was writing?
I tried writing "giberish" memory data using write.jffs2, and it didn't
complain, though. But still, its name ".jffs2" indicate that some
knowledge of jffs2 is used?
BR,
Martin Egholm
next reply other threads:[~2005-04-06 14:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-06 14:26 Martin Egholm Nielsen [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-04-07 15:10 [U-Boot-Users] JFFS2+U-Boot writing an image that has been "SUMMARY"-patched? Dave Ellis
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='d30rer$mft$1@sea.gmane.org' \
--to=martin@egholm-nielsen.dk \
--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