From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from beta.dmz-eu.st.com ([164.129.1.35]) by pentafluge.infradead.org with esmtp (Exim 3.22 #1 (Red Hat Linux)) id 17aKKQ-0001a6-00 for ; Thu, 01 Aug 2002 19:05:38 +0100 Received: from zeta.dmz-eu.st.com (zeta.dmz-eu.st.com [164.129.230.9]) by beta.dmz-eu.st.com (STMicroelectronics) with SMTP id 64A71491F for ; Thu, 1 Aug 2002 18:05:01 +0000 (GMT) Received: from thistle.bri.st.com (localhost [127.0.0.1]) by zeta.dmz-eu.st.com (STMicroelectronics) with ESMTP id EB52F1848 for ; Thu, 1 Aug 2002 18:05:00 +0000 (GMT) Received: from [164.129.14.5] (helo=ocelot) by thistle.bristol.st.com with smtp (Exim 3.03 #5) id 17aKJo-0007Xw-00 for linux-mtd@lists.infradead.org; Thu, 01 Aug 2002 19:05:00 +0100 Date: Thu, 1 Aug 2002 19:05:00 +0100 From: Stuart Menefy To: linux-mtd@lists.infradead.org Subject: Re: "Read-only file system" error while writing Message-Id: <20020801190500.7e73cf60.stuart.menefy@st.com> In-Reply-To: <28851.1028197900@redhat.com> References: <1028147069.12139.81.camel@mahi190.austin.ibm.com> <1028064443.23642.52.camel@mahi190.austin.ibm.com> <20020731163530.70c45960.stuart.menefy@st.com> <28851.1028197900@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-mtd-admin@lists.infradead.org Errors-To: linux-mtd-admin@lists.infradead.org List-Help: List-Post: List-Subscribe: , List-Id: Linux MTD discussion mailing list List-Unsubscribe: , List-Archive: On Thu, 1 Aug 2002 11:31:40 +0100 dwmw2@infradead.org wrote: > gromit1463@mailworks.org said: > > they all call do_write_buffer(). I was looking at the specsheet for > > my STMicro chips, and I didn't see any mention of Write-to-Buffer > > (command 0xE0) which is in the Intel command set, and issued by > > do_write_buffer(). Is this command supported on the STMicro chips? > > Could non-support contribute to my problem? > > We should be checking the CFI table for buffer-write support and not trying > to use it if it's not present. Can you check the datasheet for the chip > agrees with the built-in CFI table? Yes, the CFI data for this field is right (ie the device does not support Block writes). So I don't think this should be the problem. Stuart -- Stuart Menefy stuart.menefy@st.com STMicroelectronics Ltd ST Intranet: mo.bri.st.com Bristol, UK Rest of the World: www.linuxsh.st.com