Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757656AbbKSEVf (ORCPT ); Wed, 18 Nov 2015 23:21:35 -0500 Received: from mailout.micron.com ([137.201.242.129]:43881 "EHLO mailout.micron.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755610AbbKSEVe (ORCPT ); Wed, 18 Nov 2015 23:21:34 -0500 From: =?utf-8?B?QmVhbiBIdW8g6ZyN5paM5paMIChiZWFuaHVvKQ==?= To: Brian Norris CC: "linux-kernel@vger.kernel.org" , "linux-mtd@lists.infradead.org" , "Boris Brezillon" Subject: RE: enhance ONFI table reliability/stable Thread-Topic: enhance ONFI table reliability/stable Thread-Index: AQHRIa0E0lcoh1951EacZuPyMAwTpZ6ivhPQ Date: Thu, 19 Nov 2015 04:21:01 +0000 Message-ID: References: <20151118025010.GB140057@google.com> In-Reply-To: <20151118025010.GB140057@google.com> Accept-Language: zh-CN, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [137.201.21.109] X-TM-AS-Product-Ver: SMEX-11.0.0.4179-8.000.1202-21948.005 X-TM-AS-Result: No--17.345500-0.000000-31 X-TM-AS-User-Approved-Sender: Yes X-TM-AS-User-Blocked-Sender: No x-mt-checkinternalsenderrule: True Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from base64 to 8bit by mail.home.local id tAJ4LeZR023542 Content-Length: 2176 Lines: 58 > > Hi Bean, > > I was sorting through old email and I found this. > > On Tue, Jul 21, 2015 at 02:42:34PM +0000, Bean Huo 霍斌斌 (beanhuo) > wrote: > > Hi, > > > > Recently, I faced some case about ONFI table reliability, now it used CRC. > > If there is bit flips in ONFI parameter pages, parameter backup page will be > taken. > > For latest linux,default read three copys. > > > > chip->cmdfunc(mtd, NAND_CMD_PARAM, 0, -1); > > for (i = 0; i < 3; i++) { > > for (j = 0; j < sizeof(*p); j++) > > ((uint8_t *)p)[j] = chip->read_byte(mtd); > > if (onfi_crc16(ONFI_CRC_BASE, (uint8_t *)p, 254) == > > le16_to_cpu(p->crc)) { > > break; > > } > > } > > > > However ,with technoogy improvement,for TLC and new generatin MLC,I > > think, three copys of > > Ha, "improvement" :) > > > Parameter tables is not powerful enough.my question is that if there > > is a good method to protect and corrent parameter page. For example,we > > can use linux software BCH ecc. Any suggections and input be > > welcomed,if you having any concerns about this,don't free tell me. > > I recall this being brought up at my old job, and I all I can say is... > (please pardon my censored language) Yes , you ever told about this. I just follow. Sorry for my rude following. I only want to share my one suggestion about using software ECC to protect ONFI table that read from NAND. I want to hear every MTD expert 's valuable Feedback on this. if OK, I can do it. > ...that is complete and utter bulls***. An ONFI standard that can't guarantee > "reliable enough" parameter pages is no standard at all. > > To step back a bit: How would one expect to store and retrieve ECC parity > data? ...on the NAND flash? But to do that, we have to know the geometry > parameters of said NAND flash. How do we figure out the geometry? From the > ONFI parameter pages! Nice Catch 22 you have there. > > Please encourage your employer never to produce "ONFI-compliant" flash that > are this bad. > > Regards, > Brian ????{.n?+???????+%?????ݶ??w??{.n?+????{??G?????{ay?ʇڙ?,j??f???h?????????z_??(?階?ݢj"???m??????G????????????&???~???iO???z??v?^?m???? ????????I?