From: Stefan Roese <sr@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] JFFS2 with NAND flash is very SLOW ...
Date: Tue, 2 Jun 2009 15:31:58 +0200 [thread overview]
Message-ID: <200906021531.58571.sr@denx.de> (raw)
In-Reply-To: <00c601c9e385$63278660$29769320$@savary@kerlink.fr>
On Tuesday 02 June 2009 15:23:57 Pierre Savary wrote:
> Is it better to use or not D-cache and I-cache?
Depends a bit on the "application". From my experience I-Cache is most
important. But for memory intensive applications (JFFS2 might be such a beast)
D-cache could be very helpful as well. Best is to have both enabled of course.
> Currently, in my config file, I have only
> #define CONFIG_CMD_CACHE
> What do I have to add?
Defining the cache commands doesn't insure that caches are really enabled.
Some platforms don't support I- and/or D-cache in U-Boot. I can only speak for
PPC4xx which has I-cache enabled and "usually" D-cache disabled (because of
cache-coherency issues). This might be different on your platform. Again, just
enabling the cache commands will most likely not help here.
Best regards,
Stefan
=====================================================================
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: +49-8142-66989-0 Fax: +49-8142-66989-80 Email: office at denx.de
=====================================================================
next prev parent reply other threads:[~2009-06-02 13:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-02 9:21 [U-Boot] JFFS2 with NAND flash is very SLOW Pierre Savary
2009-06-02 12:22 ` Cote, Sylvain
2009-06-02 12:51 ` Pierre Savary
2009-06-02 13:02 ` Cote, Sylvain
2009-06-02 13:17 ` Stefan Roese
2009-06-02 13:23 ` Pierre Savary
2009-06-02 13:31 ` Stefan Roese [this message]
2009-06-02 13:56 ` Pierre Savary
2009-06-02 13:59 ` Stefan Roese
2009-06-02 15:06 ` Jean-Christophe PLAGNIOL-VILLARD
2009-06-02 15:30 ` Pierre Savary
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=200906021531.58571.sr@denx.de \
--to=sr@denx.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.