From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail-pz0-f49.google.com ([209.85.210.49]) by canuck.infradead.org with esmtps (Exim 4.72 #1 (Red Hat Linux)) id 1QFFMf-00023O-IW for linux-mtd@lists.infradead.org; Thu, 28 Apr 2011 00:45:54 +0000 Received: by pzk28 with SMTP id 28so1610267pzk.36 for ; Wed, 27 Apr 2011 17:45:51 -0700 (PDT) Message-ID: <4DB8B8B9.4050604@gmail.com> Date: Wed, 27 Apr 2011 17:45:45 -0700 From: Brian Norris MIME-Version: 1.0 To: Grazvydas Ignotas Subject: Re: [RFC] mtd: nand: Fix bad block identification issue References: <1303906161-24175-1-git-send-email-parth.saxena@ti.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: "Basheer, Mansoor Ahamed" , Artem Bityutskiy , "Saxena, Parth" , linux-omap@vger.kernel.org, linux-mtd@lists.infradead.org List-Id: Linux MTD discussion mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Hi, On 4/27/2011 8:45 AM, Grazvydas Ignotas wrote: > Brian, > > did you really intend to remove badblockbits? Maybe it should go back > to nand_base.c? No, I had no intention of the sorts! It surely should not have been removed in the first place. I will "ack" a patch to revert it, or next time I'm at my work machine I'll write one myself. As a defense for myself...I think I was relatively new to git + kernel hacking at the time I sent this patch. Sorry for the messup. > On Wed, Apr 27, 2011 at 3:09 PM, Saxena, Parth wrote: >> Commit e0b58d0 ("mtd: nand: add ->badblockbits for minimum number >> of set bits in bad block byte") by Maxim Levitsky added >> badblockbits to nand_chip to specify minimum number of set bits >> in bad block byte. The patch initialized badblockbits to 8 in >> nand_base.c, but later the initialization line got removed by commit >> c7b28e2("mtd: nand: refactor BB marker detection"). After this all >> NAND drivers with NAND_SKIP_BBTSCAN are forced to initialize it to 8. >> Otherwise bad block identification will fail. Brian