From: Bill Gatliff <bgat@billgatliff.com>
To: linux-mtd@lists.infradead.org
Subject: Can ID the NAND chip, but every erase block is bad?
Date: Fri, 01 Jan 2010 23:05:52 -0600 [thread overview]
Message-ID: <4B3ED430.5040607@billgatliff.com> (raw)
Guys:
I have a platform with an ancient Linux kernel that I'm updating, and
I'm having some problems. The platform has a Freescale MPC5200, a
Samsung K9 NAND flash chip, and it all works fine under 2.6.20, I'm
trying to bring it up to 2.6.32.
Simply put, when I register the gen_nand device for this chip under
2.6.32, it successfully identifies the chip but then says that every
single eraseblock in the chip is bad. When I reboot to the 2.6.20
kernel, I don't get any complaints there. I see the same problem both
with and without CONFIG_MTD_NAND_ECC_SMC.
Anyone have any ideas on where I should look for the problem? Thanks!
b.g.
--
Bill Gatliff
Embedded systems training and consulting
http://billgatliff.com
bgat@billgatliff.com
next reply other threads:[~2010-01-02 5:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-02 5:05 Bill Gatliff [this message]
2010-01-02 10:03 ` Can ID the NAND chip, but every erase block is bad? David Woodhouse
2010-01-03 13:58 ` Bill Gatliff
2010-01-03 15:44 ` Darwin Rambo
2010-01-03 15:55 ` David Woodhouse
2010-01-04 19:48 ` Bill Gatliff
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=4B3ED430.5040607@billgatliff.com \
--to=bgat@billgatliff.com \
--cc=linux-mtd@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 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.