From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail-fx0-f49.google.com ([209.85.161.49]) by bombadil.infradead.org with esmtp (Exim 4.72 #1 (Red Hat Linux)) id 1OoEcd-0006VV-Ia for linux-mtd@lists.infradead.org; Wed, 25 Aug 2010 11:58:28 +0000 Received: by fxm12 with SMTP id 12so260308fxm.36 for ; Wed, 25 Aug 2010 04:58:26 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: References: <4C607150.6040806@jkmicro.com> From: Shane Volpe Date: Wed, 25 Aug 2010 07:58:06 -0400 Message-ID: Subject: Re: buffer write error (status 0x90) To: Joakim Tjernlund Content-Type: text/plain; charset=ISO-8859-1 Cc: linux-mtd@lists.infradead.org, Adam Yergovich , Jon Ringle List-Id: Linux MTD discussion mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Tue, Aug 24, 2010 at 7:18 PM, Joakim Tjernlund wrote: > It states : > When customer uses [...] block unlock, the block lock status might be > altered inadvertently. Lock status might be set to either 01h or 03h > unexpectedly (00h as expected data), which leads to program/erase failure > on certain blocks. > > Easy to work around. Joakim, Do you have a patch or an example on how to work around this? Regards, Shane