From: Matthias Fuchs <matthias.fuchs@esd-electronics.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Non-block-skipping NAND commands (was: Loading from NAND using 'nboot' Periodically Fails Where 'nand read' Succeeds)
Date: Wed, 4 Jun 2008 09:19:18 +0200 [thread overview]
Message-ID: <200806040919.19222.matthias.fuchs@esd-electronics.com> (raw)
In-Reply-To: <48446F0D.4030205@freescale.com>
Hi Scott,
we are using the NAND stuff for a couple of boards. All use the .i or .jffs2 extension.
So I also vote for making skipping the default. But the extensions should be preserved :-)
Matthias
On Tuesday 03 June 2008 00:07, Scott Wood wrote:
> Grant Erickson wrote:
> > Thanks for the suggestion. That solved it. As an academic exercise, is there
> > any practical reason a system would want to use nboot, as I erroneously
> > chose to do, without .i|.jffs2|.e?
>
> I don't think so, though I don't know the history involved. Does anyone
> actually use the non-block-skipping versions of any of the nand commands
> (intentionally, that is)? If the answer is no, then we could make it
> the default.
>
> -Scott
next prev parent reply other threads:[~2008-06-04 7:19 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-02 1:53 [U-Boot-Users] Loading from NAND using 'nboot' Periodically Fails Where 'nand read' Succeeds Grant Erickson
2008-06-02 6:22 ` Stefan Roese
2008-06-02 18:21 ` Scott Wood
2008-06-02 22:02 ` Grant Erickson
2008-06-02 22:07 ` [U-Boot-Users] Non-block-skipping NAND commands (was: Loading from NAND using 'nboot' Periodically Fails Where 'nand read' Succeeds) Scott Wood
2008-06-03 0:48 ` Stuart Wood
2008-06-03 6:09 ` Stefan Roese
2008-06-04 7:19 ` Matthias Fuchs [this message]
2008-06-04 9:56 ` [U-Boot-Users] Non-block-skipping NAND commands Detlev Zundel
2008-06-05 20:47 ` [U-Boot-Users] Loading from NAND using 'nboot' Periodically Fails Where 'nand read' Succeeds Grant Erickson
2008-06-05 22:30 ` Grant Erickson
2008-06-05 22:59 ` Grant Erickson
2008-06-06 7:38 ` Marian Balakowicz
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=200806040919.19222.matthias.fuchs@esd-electronics.com \
--to=matthias.fuchs@esd-electronics.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.