From: Bill Gatliff <bgat@billgatliff.com>
To: David Woodhouse <dwmw2@infradead.org>
Cc: linux-mtd@lists.infradead.org
Subject: Re: Can ID the NAND chip, but every erase block is bad?
Date: Mon, 04 Jan 2010 13:48:55 -0600 [thread overview]
Message-ID: <4B424627.8090109@billgatliff.com> (raw)
In-Reply-To: <1262426622.3181.5832.camel@macbook.infradead.org>
David Woodhouse wrote:
> Take a closer look at how bad blocks were detected under 2.6.20.
>
Found the problem.
I hacked the code to show me the bytes as they were being read from the
flash, and they were significantly different with my 2.6.32 kernel---
all zeros, in fact. That led me to a bug in my cmd_ctrl code: I was
bailing out if the command was CMD_NONE, before writing anything to the
flash. That causes some important bytes to get dropped, apparently. :)
Thanks!
b.g.
--
Bill Gatliff
Embedded systems training and consulting
http://billgatliff.com
bgat@billgatliff.com
prev parent reply other threads:[~2010-01-04 19:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-02 5:05 Can ID the NAND chip, but every erase block is bad? Bill Gatliff
2010-01-02 10:03 ` 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 [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=4B424627.8090109@billgatliff.com \
--to=bgat@billgatliff.com \
--cc=dwmw2@infradead.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).