From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from gateway.prograde.net ([66.92.163.78] helo=sol.prograde.net) by canuck.infradead.org with esmtp (Exim 4.72 #1 (Red Hat Linux)) id 1Pna12-0006cc-A2 for linux-mtd@lists.infradead.org; Thu, 10 Feb 2011 17:09:13 +0000 Subject: Re: Numonyx NOR and chip->mutex bug? Mime-Version: 1.0 (Apple Message framework v1082) Content-Type: text/plain; charset=us-ascii From: Michael Cashwell In-Reply-To: Date: Thu, 10 Feb 2011 12:10:18 -0500 Content-Transfer-Encoding: quoted-printable Message-Id: <3B106371-0DA1-4F15-9482-7307110A86E2@prograde.net> References: <16826B66-31FE-41AD-A6EF-E668A45AF1FE@prograde.net> <0488D3BA-7BA3-4E98-B289-3F3D1DB485D4@prograde.net> <85661EDC-9882-41B1-A926-0A88EF1CEF2E@prograde.net> To: Joakim Tjernlund Cc: linux-mtd@lists.infradead.org, stefan.bigler@keymile.com, Holger brunck , =?iso-8859-1?Q?Anders_Grafstr=F6m?= List-Id: Linux MTD discussion mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Feb 10, 2011, at 12:02 PM, Joakim Tjernlund wrote: > And this reminds me that if the spec is to be trusted, the delay = should be just before erase suspend, otherwise you miss the time between = the initial erase and the first suspend. Probably true to be completely sure. I bet the need for "repeated = violations" is why I've been able to make it work by delaying after. But = I agree. I have an idea for an efficient fix. But it's tricky to not impact = writing speed. Once it get the idea worked out I'll post for comment. I = have some other commitments today, so honestly it'll likely be next week = at this point. -Mike