From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754755Ab1LMCmf (ORCPT ); Mon, 12 Dec 2011 21:42:35 -0500 Received: from tx2ehsobe002.messaging.microsoft.com ([65.55.88.12]:52153 "EHLO TX2EHSOBE003.bigfish.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754240Ab1LMCmd convert rfc822-to-8bit (ORCPT ); Mon, 12 Dec 2011 21:42:33 -0500 X-SpamScore: -14 X-BigFish: VS-14(zzbb2dI9371Ic89bh936eK1432N98dKzz1202hzzz2dh2a8h668h839h93fh61h) X-Spam-TCS-SCL: 0:0 X-Forefront-Antispam-Report: CIP:70.37.183.190;KIP:(null);UIP:(null);IPV:NLI;H:mail.freescale.net;RD:none;EFVD:NLI Message-ID: <4EE6BC9B.4000602@freescale.com> Date: Tue, 13 Dec 2011 10:46:51 +0800 From: LiuShuo User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.14) Gecko/20110223 Thunderbird/3.1.8 MIME-Version: 1.0 To: Scott Wood CC: , , , , , , , , Subject: Re: [PATCH 3/3] mtd/nand : workaround for Freescale FCM to support large-page Nand chip References: <1322973098-2528-1-git-send-email-shuo.liu@freescale.com> <1322973098-2528-3-git-send-email-shuo.liu@freescale.com> <4EDEAEB9.6020703@freescale.com> <1323724195.2297.11.camel@koala> <4EE66EFE.1050608@freescale.com> <1323724784.2297.20.camel@koala> <4EE6725C.3050706@freescale.com> In-Reply-To: <4EE6725C.3050706@freescale.com> Content-Type: text/plain; charset="UTF-8"; format=flowed Content-Transfer-Encoding: 8BIT X-OriginatorOrg: freescale.com Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 于 2011年12月13日 05:30, Scott Wood 写道: > 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 data, 64 >>> byte oob, 2k data, 64 byte oob" the marker is no longer in the oob. On >>> first use we need to migrate the markers so that they are still in 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 > Most likely is a firmware-based tool, but I'd like there to be some way > 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 having > 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