From: Anders Grafstrom <grfstrm@users.sourceforge.net>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Problem with JFFS2 summary on NOR-flash
Date: Tue, 11 Apr 2006 14:53:11 +0200 [thread overview]
Message-ID: <443BA6B7.5070807@users.sourceforge.net> (raw)
Hello,
I tried to use the summary feature of JFFS2 on NOR-flash and ended up
with U-boot failing to read the filesystem. The reason for this turned
out to be that the JFFS2 scanning code in U-boot makes a write to the
flash memory area.
Unlinked dirents are not marked obsolete when summary is enabled and
this leads U-Boot to the line "jOld->ino = 0;" in compare_dirents().
jOld points to flash memory in the case of NOR-flash.
Without dcache this problem is not noticed as 0x00 seems to be a NOOP.
But with dcache you get either an exception if you have ROM protection
enabled or the flash chip might flip into read query mode when the cache
line is written. The latter happened for me.
I tried implementing get_fl_mem() with malloc() similar to the NAND code
but this made things VERY slow. I'm guessing that removing the
problematic line and making the code somehow sort out the highest
version of the dirents is better?
Regards, Anders
reply other threads:[~2006-04-11 12:53 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=443BA6B7.5070807@users.sourceforge.net \
--to=grfstrm@users.sourceforge.net \
--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