From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail-we0-f177.google.com ([74.125.82.177]) by merlin.infradead.org with esmtps (Exim 4.76 #1 (Red Hat Linux)) id 1Sl3sn-0002wU-59 for linux-mtd@lists.infradead.org; Sat, 30 Jun 2012 20:03:06 +0000 Received: by werb13 with SMTP id b13so50515wer.36 for ; Sat, 30 Jun 2012 13:03:01 -0700 (PDT) Date: Sat, 30 Jun 2012 23:02:52 +0300 From: Shmulik Ladkani To: Matthieu CASTET Subject: Re: [RFC] nand_btt : use nand chip->block_bad Message-ID: <20120630230252.58ca6bb4@halley> In-Reply-To: <4FED6A2E.9010603@parrot.com> References: <1340898442-1585-1-git-send-email-matthieu.castet@parrot.com> <20120628213146.7d929204@halley> <4FED6A2E.9010603@parrot.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: Brian Norris , "linux-mtd@lists.infradead.org" List-Id: Linux MTD discussion mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Hi, On Fri, 29 Jun 2012 10:41:18 +0200 Matthieu CASTET wrote: > > - The new scheme lacks the potential error correction offered by the > > mtd_read_oob call (invoked from the original scan functions). > > OTOH, currently, AFAIK, it is only offered by an out-of-tree driver. > Could you explain more here ? > The current scheme doesn't handle bitflip in bad block. We don't care about > error correction : bad block are not protected by ecc ! I was refering to utilizing the ECC when reading the OOB, so we won't get a false "bad" indication when reading the BBM from the OOB. See this post (and subsequent ones): http://lists.infradead.org/pipermail/linux-mtd/2012-June/042203.html Regards, Shmulik