From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mms1.broadcom.com ([216.31.210.17]) by bombadil.infradead.org with esmtp (Exim 4.72 #1 (Red Hat Linux)) id 1OmVcI-0007LS-U6 for linux-mtd@lists.infradead.org; Fri, 20 Aug 2010 17:42:59 +0000 Message-ID: <4C6EBE90.2090604@broadcom.com> Date: Fri, 20 Aug 2010 10:42:40 -0700 From: "Brian Norris" MIME-Version: 1.0 To: "Tilman Sauerbeck" Subject: Re: Bad assumption about ID field definition for Samsung NAND? References: <20100818180538.GA12238@code-monkey.de> <4C6C6BFC.9020408@broadcom.com> <20100819171558.GA8536@code-monkey.de> <4C6DAFFD.4040602@broadcom.com> <20100820134316.GA437@code-monkey.de> In-Reply-To: <20100820134316.GA437@code-monkey.de> Content-Type: text/plain; charset=iso-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: r64343@freescale.com, Kevin Cernekee , "linux-mtd@lists.infradead.org" List-Id: Linux MTD discussion mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On 08/20/2010 06:43 AM, Tilman Sauerbeck wrote: > Okay, how do we proceed? Should I send a proper patch with the diff > above? Or does anyone want to try and come up with a better fix...? I vote for Tilman's patch. There's nothing unnecessarily ugly about it; it simply checks cell-type in order to decide whether we use Samsung's new "standard" for MLC or fall-back to the real standard. If anything, the existing code (checking ID length) is ugly. However, both checks seem necessary. Brian