From: LiuShuo <b35362@freescale•com>
To: Scott Wood <scottwood@freescale•com>, <dedekind1@gmail•com>
Cc: Artem.Bityutskiy@nokia•com, linuxppc-dev@lists•ozlabs.org,
linux-kernel@vger•kernel.org, shuo.liu@freescale•com,
linux-mtd@lists•infradead.org, akpm@linux-foundation•org,
dwmw2@infradead•org
Subject: Re: [PATCH 3/3] mtd/nand : workaround for Freescale FCM to support large-page Nand chip
Date: Wed, 14 Dec 2011 16:41:16 +0800 [thread overview]
Message-ID: <4EE8612C.9050104@freescale.com> (raw)
In-Reply-To: <4EE6BC9B.4000602@freescale.com>
=E4=BA=8E 2011=E5=B9=B412=E6=9C=8813=E6=97=A5 10:46, LiuShuo =E5=86=99=E9=
=81=93:
> =E4=BA=8E 2011=E5=B9=B412=E6=9C=8813=E6=97=A5 05:30, Scott Wood =E5=86=99=
=E9=81=93:
>> On 12/12/2011 03:19 PM, Artem Bityutskiy wrote:
>>> On Mon, 2011-12-12 at 15:15 -0600, Scott Wood wrote:
>>>> NAND chips come from the factory with bad blocks marked at a certain
>>>> offset into each page. This offset is normally in the OOB area, but
>>>> since we change the layout from "4k data, 128 byte oob" to "2k=20
>>>> data, 64
>>>> byte oob, 2k data, 64 byte oob" the marker is no longer in the=20
>>>> oob. On
>>>> first use we need to migrate the markers so that they are still in=20
>>>> the oob.
>>> Ah, I see, thanks. Are you planning to implement in-kernel migration =
or
>>> use a user-space tool?
>> That's the kind of answer I was hoping to get from Shuo. :-)
> OK, I try to do this. Wait for a couple of days.
>
> -LiuShuo
I found it's too complex to do the migration in Linux driver.
Maybe we can add a uboot command (e.g. nand bbmigrate) to do it, once is=20
enough.
And let user ensure it been completed before linux use the Nand flash chi=
p.
Even if we don't do the migration, the bad block also can be marked as ba=
d
by wearing. So, do we really need to take much time to implement it ?
(code looks too complex.)
-LiuShuo
>> Most likely is a firmware-based tool, but I'd like there to be some wa=
y
>> for the tool to mark that this has happened, so that the Linux driver
>> can refuse to do non-raw accesses to a chip that isn't marked as havin=
g
>> been migrated (or at least yell loudly in the log).
>>
>> Speaking of raw accesses, these are currently broken in the eLBC
>> driver... we need some way for the generic layer to tell us what kind =
of
>> access it is before the transaction starts, not once it wants to read
>> out the buffer (unless we add more hacks to delay the start of a read
>> transaction until first buffer access...). We'd be better off with a
>> high-level "read page/write page" function that does the whole thing
>> (not just buffer access, but command issuance as well).
>>
>> -Scott
>
next prev parent reply other threads:[~2011-12-14 8:37 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-04 4:31 [PATCH 1/3] mtd/nand : use elbc_fcm_ctrl->oob to set FPAR_MS bit of FPAR shuo.liu
2011-12-04 4:31 ` [PATCH 2/3] mtd/nand : set correct length to FBCR for a non-full-page write shuo.liu
2011-12-04 4:31 ` [PATCH 3/3] mtd/nand : workaround for Freescale FCM to support large-page Nand chip shuo.liu
2011-12-05 6:47 ` Artem Bityutskiy
2011-12-05 19:46 ` Scott Wood
2011-12-06 11:49 ` Artem Bityutskiy
2011-12-06 11:49 ` Artem Bityutskiy
2011-12-07 0:09 ` Scott Wood
2011-12-07 3:55 ` LiuShuo
2011-12-07 19:11 ` Scott Wood
2011-12-08 10:44 ` LiuShuo
2011-12-08 18:43 ` Scott Wood
2011-12-12 21:09 ` Artem Bityutskiy
2011-12-12 21:15 ` Scott Wood
2011-12-12 21:19 ` Artem Bityutskiy
2011-12-12 21:30 ` Scott Wood
2011-12-13 2:46 ` LiuShuo
2011-12-14 8:41 ` LiuShuo [this message]
2011-12-14 20:15 ` Scott Wood
2011-12-15 4:59 ` Li Yang
2011-12-15 17:32 ` Scott Wood
2011-12-16 2:44 ` LiuShuo
2011-12-16 17:59 ` Scott Wood
2011-12-19 11:05 ` Li Yang
2011-12-19 16:47 ` Scott Wood
2011-12-20 9:08 ` Li Yang
2011-12-20 19:48 ` Scott Wood
2011-12-17 14:35 ` Artem Bityutskiy
2011-12-19 18:38 ` Scott Wood
2011-12-19 18:42 ` Scott Wood
2011-12-14 3:41 ` LiuShuo
2011-12-14 20:53 ` Scott Wood
2011-12-05 6:50 ` [PATCH 1/3] mtd/nand : use elbc_fcm_ctrl->oob to set FPAR_MS bit of FPAR Artem Bityutskiy
-- strict thread matches above, loose matches on Subject: below --
2011-11-24 0:41 b35362
2011-11-24 0:41 ` [PATCH 3/3] mtd/nand : workaround for Freescale FCM to support large-page Nand chip b35362
2011-11-24 7:37 ` Li Yang-R58472
2011-11-28 17:20 ` Scott Wood
2011-11-24 7:41 ` Artem Bityutskiy
2011-11-24 7:49 ` Li Yang-R58472
2011-11-24 8:16 ` Artem Bityutskiy
2011-11-24 10:02 ` LiuShuo
2011-11-24 11:07 ` Artem Bityutskiy
2011-11-28 21:48 ` Scott Wood
2011-11-28 21:49 ` 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=4EE8612C.9050104@freescale.com \
--to=b35362@freescale$(echo .)com \
--cc=Artem.Bityutskiy@nokia$(echo .)com \
--cc=akpm@linux-foundation$(echo .)org \
--cc=dedekind1@gmail$(echo .)com \
--cc=dwmw2@infradead$(echo .)org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-mtd@lists$(echo .)infradead.org \
--cc=linuxppc-dev@lists$(echo .)ozlabs.org \
--cc=scottwood@freescale$(echo .)com \
--cc=shuo.liu@freescale$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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