public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Pierre Savary <pierre.savary@kerlink.fr>
To: u-boot@lists.denx.de
Subject: [U-Boot] JFFS2 with NAND flash is very SLOW ...
Date: Tue, 2 Jun 2009 17:30:08 +0200	[thread overview]
Message-ID: <00d401c9e397$03a06560$0ae13020$@savary@kerlink.fr> (raw)
In-Reply-To: <20090602150609.GI6399@game.jcrosoft.org>

Which source code? I use the 2009.03 version without modification.
This is my config file:
[...]
#define CONFIG_CMD_NAND
#define CONFIG_SYS_MAX_FLASH_BANKS	1
#define CONFIG_SYS_MAX_NAND_DEVICE	1
#define CONFIG_SYS_NAND_BASE		0x20020000
#define NAND_MAX_CHIPS			1
#define CONFIG_ENV_IS_IN_NAND
[...]
#define CONFIG_CMD_JFFS2
[...]
#define CONFIG_JFFS2_NAND
#undef CONFIG_JFFS2_CMDLINE
#define CONFIG_JFFS2_DEV		"nand0"
#define CONFIG_JFFS2_PART_SIZE	0x00C00000
#define CONFIG_JFFS2_PART_OFFSET	0x000C8000
[...]
#define CONFIG_ICACHE_ON
#define CONFIG_DCACHE_ON
#define CONFIG_SYS_DCACHE_SIZE          32768
#define CONFIG_SYS_ICACHE_SIZE          32768
#define CONFIG_SYS_CACHELINE_SIZE       32
[...]

And in fact it is better with I-Cache enabled. I carried out more precise
measurements and I obtain: 1min45 without I-cache and 40sec with I-cache. It
is better but not enough...

Thanks for your help.
Best Regards,

Pierre


-----Message d'origine-----
De?: u-boot-bounces at lists.denx.de [mailto:u-boot-bounces at lists.denx.de] De
la part de Jean-Christophe PLAGNIOL-VILLARD
Envoy??: mardi 2 juin 2009 17:06
??: Stefan Roese
Cc?: Pierre Savary; 'Cote, Sylvain'; u-boot at lists.denx.de
Objet?: Re: [U-Boot] JFFS2 with NAND flash is very SLOW ...

On 15:59 Tue 02 Jun     , Stefan Roese wrote:
> On Tuesday 02 June 2009 15:56:25 Pierre Savary wrote:
> > In fact it is not better with this config:
> > #define CONFIG_ICACHE_ON
> > #define CONFIG_DCACHE_ON
> > #define CONFIG_SYS_DCACHE_SIZE          32768
> > #define CONFIG_SYS_ICACHE_SIZE          32768
> > #define CONFIG_SYS_CACHELINE_SIZE       32
> >
> > My architecture is arm926ejs and it seems that CACHE management is not
> > implemented...
> >
> > I just measure a load of uImage (2MB) ... it takes more than 2 minutes
:-(
> 
> Yes, this is really slow. Jean-Christophe will be able to tell us if
caches 
> are supported on this platform in U-Boot.
I've not yet find time to implement the MMU support for arm (needed for
D-Cache support), I've plan to add it for the next release (not for this
next
merge window)

I-Cache is supported

but 2 mins is really slow, could show us your code?

Best Regards,
J.
_______________________________________________
U-Boot mailing list
U-Boot at lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot

      reply	other threads:[~2009-06-02 15:30 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
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 [this message]

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='00d401c9e397$03a06560$0ae13020$@savary@kerlink.fr' \
    --to=pierre.savary@kerlink.fr \
    --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