From: Scott Wood <scottwood@freescale.com>
To: <b35362@freescale.com>
Cc: linuxppc-dev@ozlabs.org, dwmw2@infradead.org,
linux-mtd@lists.infradead.org
Subject: Re: [PATCH v3] mtd/nand : workaround for Freescale FCM to support large-page Nand chip
Date: Thu, 18 Aug 2011 13:27:17 -0500 [thread overview]
Message-ID: <4E4D5985.3080300@freescale.com> (raw)
In-Reply-To: <4E4D3CE0.7020602@freescale.com>
On 08/18/2011 11:25 AM, Scott Wood wrote:
> The NOP restrictions should be documented in the code itself, not just
> in the git changelog. Maybe print it to the console when this hack is
> used, along with the NOP value read from the ID. If it's less than 4
> for 4K or 8 for 8K, also print a message saying not to use jffs2 (does
> yaffs2 do similar things?). If it's less than 2 for 4K or 4 for 8K, the
> probe should fail.
We should also warn the user about the need to prepare the NAND chip by
copying the bad block markers to the OOB of the new layout.
-Scott
next prev parent reply other threads:[~2011-08-18 18:27 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-18 2:33 [PATCH v3] mtd/nand : workaround for Freescale FCM to support large-page Nand chip b35362
2011-08-18 16:25 ` Scott Wood
2011-08-18 18:27 ` Scott Wood [this message]
2011-08-23 8:37 ` LiuShuo
2011-08-23 10:02 ` Matthieu CASTET
2011-08-23 16:12 ` Scott Wood
2011-08-25 11:18 ` Artem Bityutskiy
2011-08-24 2:48 ` LiuShuo
2011-08-25 11:25 ` Matthieu CASTET
2011-09-01 9:41 ` LiuShuo
2011-09-01 22:30 ` Scott Wood
2011-08-18 17:00 ` Matthieu CASTET
2011-08-18 18:24 ` Scott Wood
2011-08-19 3:20 ` LiuShuo
2011-08-19 8:57 ` Matthieu CASTET
2011-08-19 18:10 ` Scott Wood
2011-08-22 10:58 ` Artem Bityutskiy
2011-08-22 15:25 ` Ivan Djelic
2011-08-22 16:04 ` Scott Wood
2011-08-22 16:13 ` Matthieu CASTET
2011-08-22 16:19 ` Scott Wood
2011-08-22 17:05 ` Matthieu CASTET
2011-08-23 3:09 ` LiuShuo
2011-08-23 8:14 ` Matthieu CASTET
2011-08-23 9:57 ` LiuShuo
2011-08-23 10:13 ` Matthieu CASTET
2011-08-22 15:58 ` Scott Wood
2011-08-25 11:06 ` Artem Bityutskiy
2011-08-22 10:53 ` Artem Bityutskiy
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=4E4D5985.3080300@freescale.com \
--to=scottwood@freescale.com \
--cc=b35362@freescale.com \
--cc=dwmw2@infradead.org \
--cc=linux-mtd@lists.infradead.org \
--cc=linuxppc-dev@ozlabs.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