All of lore.kernel.org
 help / color / mirror / Atom feed
From: Derek Ou <derek@siconix.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] NAND issues
Date: Fri, 13 Feb 2009 10:39:34 -0700	[thread overview]
Message-ID: <4995B056.5040005@siconix.com> (raw)

I have a few issues/questions regarding the NAND commands in the latest 
git main tree.
1) The nand_util.c does not have WATCHDOG_RESET() in the 
nand_read_skip_bad() and nand_write_skip_bad() while the original 
nand_write_opts() and nand_read_opts() do.  Is there a special reason 
this is removed?  It's likely that watchdog will fail when trying to 
read/write large files from NAND.

2) "nand write.jffs2" used to allow writing non page-aligned data.  So 
we can have scripts like "tftp 0x22000000 u-boot.bin" and "nand 
write.jffs2 0x22000000 0x20000 $(filesize)" to automate downloading 
files to NAND.  Now, "nand write(.jffs2)" and nand_write_skip_bad() 
rejects non page-aligned write.  I think we have to either pad the 
binary file to page-aligned or re-write nand_write_skip_bad().  Is there 
another way/parameter to write non page-aligned data?

3) In common/cmd_nand.c, nand_load_image() starting at at line 492 call 
nand_read() at line 514 and line 547.  Does it mean that 
nand_load_image() will read NAND bad blocks?  Should they be 
nand_read_skip_bad() instead?  Especially, line 546 has this comment     
/* FIXME: skip bad blocks */

Thanks,
Derek

             reply	other threads:[~2009-02-13 17:39 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-13 17:39 Derek Ou [this message]
2009-02-13 20:37 ` [U-Boot] NAND issues Scott Wood
  -- strict thread matches above, loose matches on Subject: below --
2009-08-12  5:30 alfred steele
2009-08-12 19:44 ` Scott Wood
     [not found]   ` <528f13590908121811m5d23b0cewcc7ac572a6870c51@mail.gmail.com>
2009-08-13  1:21     ` alfred steele
2009-08-13 15:11       ` Scott Wood
2009-08-13 22:58         ` alfred steele
2009-08-14 15:37           ` Scott Wood

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=4995B056.5040005@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 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.