From: Steve Sakoman <steve@sakoman.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] fw_setenv broken?
Date: Thu, 18 Nov 2010 16:33:43 -0800 [thread overview]
Message-ID: <1290126823.2927.1623.camel@quadra> (raw)
In-Reply-To: <20101118182014.75730ae2@udp111988uds.am.freescale.net>
On Thu, 2010-11-18 at 18:20 -0600, Scott Wood wrote:
> On Thu, 18 Nov 2010 16:13:52 -0800
> Steve Sakoman <steve@sakoman.com> wrote:
>
> > The code generating both errors is in the nand_do_read_ops function in nand_base.c:
> >
> > if (mtd->ecc_stats.failed - stats.failed)
> > return -EBADMSG;
> >
> > return mtd->ecc_stats.corrected - stats.corrected ? -EUCLEAN : 0;
> > }
> >
> > I understand that the -EUCLEAN error indicates a correctable ECC error. What does the -EBADMSG error indicate?
>
> An uncorrectable ECC error (or other failure).
>
> > This condition doesn't seem to bother the linux driver, but u-boot doesn't like it at all!
>
> Check whether the ECC layout and code is the same for this driver in
> both U-Boot and Linux.
Since fw_printenv in Linux always can successfully read an environment
written by U-boot (aqs well as those written by fw_setenv), wouldn't
this indicate that they are using the same ECC layout? If they were
different I would expect that compatibility in both directions would be
broken.
This is not my area of expertise, so perhaps I am just ignorant of how
things work.
Steve
next prev parent reply other threads:[~2010-11-19 0:33 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-17 16:30 [U-Boot] fw_setenv broken? Steve Sakoman
2010-11-17 16:56 ` Stefano Babic
2010-11-17 17:39 ` Wolfgang Denk
2010-11-17 17:51 ` Steve Sakoman
2010-11-17 18:13 ` Mike Frysinger
2010-11-17 18:28 ` Wolfgang Denk
2010-11-17 20:05 ` Steve Sakoman
2010-11-17 20:47 ` Wolfgang Denk
2010-11-17 21:29 ` Steve Sakoman
2010-11-17 21:40 ` Wolfgang Denk
2010-11-17 21:55 ` Steve Sakoman
2010-11-17 22:08 ` Scott Wood
2010-11-17 22:48 ` Steve Sakoman
2010-11-17 23:05 ` Wolfgang Denk
2010-11-19 0:13 ` Steve Sakoman
2010-11-19 0:20 ` Scott Wood
2010-11-19 0:33 ` Steve Sakoman [this message]
2010-11-19 5:09 ` Steve Sakoman
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=1290126823.2927.1623.camel@quadra \
--to=steve@sakoman.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.