From: "Marc Reilly" <marc@cpdesign.com.au>
To: barebox@lists.infradead.org
Subject: Way to clear nand bad block table
Date: Thu, 26 Jul 2012 18:25:24 +1000 [thread overview]
Message-ID: <002601cd6b08$37498d50$a5dca7f0$@cpdesign.com.au> (raw)
Hi,
Is there a way to clear the nand bad block table?
I'm not sure what happened, but I was playing around with barebox init and
didn't register the nand device - then when I booted the kernel there were a
stack of UBI errors.
I assume this also did something to the bbt as subsequent barebox startups
give a heap of bad block messages. Note not all blocks are bad - tested with
nandtest and there's still some R/W going on.
All the code I looked at seemed to indicate that once a block is marked bad
you can't go back.
Any ideas much appreciated.
Cheers,
Marc
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next reply other threads:[~2012-07-26 8:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-26 8:25 Marc Reilly [this message]
2012-07-26 9:27 ` Juergen Beisert
2012-07-27 1:24 ` Marc Reilly
2012-07-27 7:53 ` Sascha Hauer
2012-07-27 8:31 ` RFC: How to setup and handle NAND flashes in Barebox Juergen Beisert
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='002601cd6b08$37498d50$a5dca7f0$@cpdesign.com.au' \
--to=marc@cpdesign.com.au \
--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