From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from lotus.glocalnet.net ([213.163.128.201]) by canuck.infradead.org with esmtp (Exim 4.54 #1 (Red Hat Linux)) id 1FLfIn-0007gv-EW for linux-mtd@lists.infradead.org; Tue, 21 Mar 2006 06:45:41 -0500 To: linux-mtd@lists.infradead.org References: <1142865089.c65a3380tomas2003@home.se> Message-ID: From: Tomas Content-Type: text/plain; format=flowed; charset=iso-8859-15 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Date: Tue, 21 Mar 2006 12:43:45 +0100 In-Reply-To: Subject: Re: cfi 0001 List-Id: Linux MTD discussion mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Hi, There are 2 things that I didn't expect: First that the flash allways seems to be in non-readable state after a write. It will not change state until a read is performed. This might be by design for performance? The cfi-driver uses the buffered write and then returns. Next time the cfi-driver is called it checks if the operation done before was completed and issue the current task? The second thing is that it whole flash is put into a non-readable state in a write operation. I have partition the flash in several partition by using physmap. I don't know how the cfi flash works but shoudn't it be possible to work on sector basis? Thanks in advance, Tomas