All of lore.kernel.org
 help / color / mirror / Atom feed
From: Scott Wood <scottwood@freescale.com>
To: avorontsov@ru.mvista.com
Cc: linux-mtd@lists.infradead.org,
	David Woodhouse <dwmw2@infradead.org>,
	Iwo Mergler <iwo@call-direct.com.au>
Subject: Re: [PATCH] MTD: NAND: fsl_elbc_nand: implement support for	flash-based BBT
Date: Fri, 27 Jun 2008 10:30:34 -0500	[thread overview]
Message-ID: <4865079A.2020300@freescale.com> (raw)
In-Reply-To: <20080627145512.GA11372@polina.dev.rtsoft.ru>

Anton Vorontsov wrote:
> Just looked into x16 LP NAND spec, and it says that block should be
> considered as bad when the first _Word_ isn't 0xff. So we indeed should
> not ignore the second byte. Ouch.

The FCM doesn't support 16-bit devices.

> How about this patch?

ACK

-Scott

  reply	other threads:[~2008-06-27 15:30 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
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 [this message]
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=4865079A.2020300@freescale.com \
    --to=scottwood@freescale.com \
    --cc=avorontsov@ru.mvista.com \
    --cc=dwmw2@infradead.org \
    --cc=iwo@call-direct.com.au \
    --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.