mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Jon Ringle <jon@ringle.org>
To: barebox@lists.infradead.org
Subject: Re: barebox nand ignoring bad eraseblocks or read/write
Date: Sun, 11 Sep 2011 21:35:29 -0400	[thread overview]
Message-ID: <CAMwGMjwFt=bjhWmPKDUCWUjGBTULb9U33=GfrDUcFtrQW4107A@mail.gmail.com> (raw)
In-Reply-To: <CAMwGMjyne+ixbgzJ3_KJ9+=qHK+kGQgQGqL06stVvv-GQ6PYow@mail.gmail.com>

On Fri, Sep 9, 2011 at 11:29 PM, Jon Ringle <jon@ringle.org> wrote:
> I have a NAND device with a few bad eraseblocks, which is not
> uncommon. I figured that barebox would properly handle avoiding the
> bad eraseblocks.
> So I was surprised when I discovered that this is not entirely the
> case when I #define DEBUG at the top of nand.c. erase seems to honor
> the bad eraseblocks, but write still silently uses the bad erase block
> and read fails when it reads the bad eraseblock at 0x001e0000. Am I
> missing something?

I found that I had CONFIG_GLOB=n and that was causing
/env/bin/hush_hack to fail to create the bad block aware devices with
"nand -a /dev/nand0.*"

Jon

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

      reply	other threads:[~2011-09-12  1:35 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-10  3:29 Jon Ringle
2011-09-12  1:35 ` Jon Ringle [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='CAMwGMjwFt=bjhWmPKDUCWUjGBTULb9U33=GfrDUcFtrQW4107A@mail.gmail.com' \
    --to=jon@ringle.org \
    --cc=barebox@lists.infradead.org \
    /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