From: "Andriy Korud" <a.korud@vector.com.pl>
To: <linux-mtd@lists.infradead.org>
Subject: Please explain bbt_create (problems)
Date: Fri, 15 Jul 2005 16:18:34 +0200 [thread overview]
Message-ID: <60E856FD577CC04BA3727AF4122D3F161135CD@3bit.vector.com.pl> (raw)
Hi,
I'm trying to understand how initial bbt_ceate works?
I have NAND chip erased for jffs2 (flash_erasall -j) with some data in OOB (jffs2 clean masrkers). And bbt_create() calls check_pattern() which compare each byte with 0xff, in my case comparision fails (jffs2 cleanmarker != 0xff) and I have every block marked as bad.
Should not check_pattern() checks only byte at 0x05 in OOB (according to http://www.linux-mtd.infradead.org/tech/mtdnand/x255.html )?
Also is it possible to scan chip for bbt starting from certain block (not 0) without dirty changes in mtd code?
Thanks in advance,
Andriy Korud
next reply other threads:[~2005-07-15 14:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-15 14:18 Andriy Korud [this message]
2005-07-15 14:40 ` Please explain bbt_create (problems) Thomas Gleixner
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=60E856FD577CC04BA3727AF4122D3F161135CD@3bit.vector.com.pl \
--to=a.korud@vector.com.pl \
--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