From: Scott Wood <scottwood@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Nand dump and nand bad block disagree
Date: Wed, 29 Feb 2012 13:11:09 -0600 [thread overview]
Message-ID: <4F4E784D.2070506@freescale.com> (raw)
In-Reply-To: <CAGGh5h21Oue6dgcs1+XzC06B_oQxWgG=Po7V7WHuac+PGDDLyw@mail.gmail.com>
On 02/29/2012 03:02 AM, jean-philippe francois wrote:
> Le 29 f?vrier 2012 00:40, Scott Wood <scottwood@freescale.com> a ?crit :
>> Also please mention which version of U-Boot you're using. Top of tree
>> currently has broken nand dump (fixed with the latest nand pull request).
>>
> I am using a pretty ancient version (2009.11) because it is the version
> provided with Ti DVSDK.
You may want to check whether current upstream U-Boot runs on your hardware.
Otherwise, ask TI for support with their SDK.
-Scott
prev parent reply other threads:[~2012-02-29 19:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-28 14:34 [U-Boot] Nand dump and nand bad block disagree jean-philippe francois
2012-02-28 23:40 ` Scott Wood
2012-02-29 9:02 ` jean-philippe francois
2012-02-29 19:06 ` Mike Frysinger
2012-02-29 19:09 ` Scott Wood
2012-02-29 22:34 ` Mike Frysinger
2012-02-29 22:37 ` Scott Wood
2012-02-29 22:54 ` Mike Frysinger
2012-02-29 23:14 ` Scott Wood
2012-02-29 19:11 ` Scott Wood [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=4F4E784D.2070506@freescale.com \
--to=scottwood@freescale.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.