From: Scott Wood <scottwood@freescale.com>
To: Anton Vorontsov <avorontsov@ru.mvista.com>
Cc: linux-mtd@lists.infradead.org, David Woodhouse <dwmw2@infradead.org>
Subject: Re: [PATCH] MTD: NAND: fsl_elbc_nand: fix OOB workability for large page NAND chips
Date: Thu, 26 Jun 2008 13:59:45 -0500 [thread overview]
Message-ID: <4863E721.60906@freescale.com> (raw)
In-Reply-To: <20080626184156.GA2356@polina.dev.rtsoft.ru>
Anton Vorontsov wrote:
> For large page chips, nand_bbt is looking into OOB area, and checking
> for "0xff 0xff" pattern at OOB offset 0. That is, two bytes should be
> reserved for bbt means.
Interesting... both the 8313 manual and the manual for a random large
page NAND chip say that the bad block indicator is one byte.
BTW, I was just looking at NAND boot on this chip, and it seems that it
expects ECCM=1 for large page devices, so we should make that the
default (preferably at the same time as we fix this problem, so that we
don't break compatibility with a working version).
-Scott
next prev parent reply other threads:[~2008-06-26 18:59 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-26 18:41 [PATCH] MTD: NAND: fsl_elbc_nand: fix OOB workability for large page NAND chips Anton Vorontsov
2008-06-26 18:59 ` Scott Wood [this message]
2008-06-26 23:06 ` Anton Vorontsov
2008-06-27 14:43 ` Scott Wood
2008-06-27 15:04 ` Anton Vorontsov
2008-06-27 6:19 ` Iwo Mergler
2008-06-27 14:55 ` [PATCH] MTD: NAND: fsl_elbc_nand: implement support for flash-based BBT Anton Vorontsov
2008-06-27 15:30 ` Scott Wood
2008-06-27 16:00 ` Anton Vorontsov
2008-06-27 16:29 ` Scott Wood
2008-06-27 19:02 ` Anton Vorontsov
2008-06-27 19:04 ` [PATCH 1/3] MTD: NAND: fsl_elbc_nand: fix OOB workability for large page NAND chips Anton Vorontsov
2008-06-27 19:04 ` [PATCH 2/3] MTD: NAND: fsl_elbc_nand: implement support for flash-based BBT Anton Vorontsov
2008-06-27 19:04 ` [PATCH 3/3] MTD: NAND: fsl_elbc_nand: ecclayout cleanups Anton Vorontsov
2008-06-30 21:09 ` Scott Wood
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=4863E721.60906@freescale.com \
--to=scottwood@freescale.com \
--cc=avorontsov@ru.mvista.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 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.