public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Derek Ou <derek@siconix.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] scan jffs2 NAND slow and bad block
Date: Tue, 09 Dec 2008 16:56:39 -0700	[thread overview]
Message-ID: <493F05B7.70307@siconix.com> (raw)

Dear all,

I just enabled CMD_JFFS2 and JFFS2_NAND in the uboot 1.3.4 for my 
at91sam9263 based board.  In general,  it works in loading the jffs2 
file system and loading files from it.  However, it takes almost an hour 
to scan the jffs2 partition, which is 512 MiB.  Is it because of the 
size of the partition?  Linux loads and starts within a minute.  How 
come it takes so long for u-boot?

Also, it seems that fsload/scanning FS routine does not skip the bad 
blocks in NAND.  So it complains about "read_nand_cached: error reading 
nand off 0x########", with the address within bad blocks reported by 
"nand bad".  Did I forget something in the configuration?

Thanks,
Derek

******** my related configuration ********
#undef CONFIG_CMD_FLASH
#define CONFIG_CMD_NAND        1
#define CONFIG_CMD_JFFS2
#define NAND_MAX_CHIPS            1
#define CFG_MAX_NAND_DEVICE        1
#define CFG_NAND_BASE            0x40000000
#define CFG_NAND_DBW_8            1
#undef CONFIG_JFFS2_CMDLINE
#define CONFIG_JFFS2_NAND            1
#define CONFIG_JFFS2_DEV            "nand0"
#define CONFIG_JFFS2_PART_SIZE        0x20000000
#define CONFIG_JFFS2_PART_OFFSET    0

             reply	other threads:[~2008-12-09 23:56 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-09 23:56 Derek Ou [this message]
2008-12-10  0:27 ` [U-Boot] scan jffs2 NAND slow and bad block Wolfgang Denk

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=493F05B7.70307@siconix.com \
    --to=derek@siconix.com \
    --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