From: Stuart Menefy <stuart.menefy@st.com>
To: linux-mtd@lists.infradead.org
Subject: Re: "Read-only file system" error while writing
Date: Thu, 1 Aug 2002 19:26:24 +0100 [thread overview]
Message-ID: <20020801192624.28fe7b7e.stuart.menefy@st.com> (raw)
In-Reply-To: <20020801190500.7e73cf60.stuart.menefy@st.com>
On Thu, 1 Aug 2002 19:05:00 +0100
stuart.menefy@st.com wrote:
> 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.
Sorry, I should have read the email more closely before replying.
For the M28W320CB which I'm using, the CFI data is correct, in that it
reports that the device does not support Block writes. Stephen is using the
M28W320CT, which will have different CFI data, so maybe it is reporting that
it is supported?
The datasheet is no use in this respect, in its listing of the CFI data it
gives times for buffer-writes, which the device does not support!
Try building cfi_probe.c with DEBUG_CFI set, and post what it reports.
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
next prev parent reply other threads:[~2002-08-01 18:28 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-30 21:27 "Read-only file system" error while writing Stephen Hui
2002-07-30 22:25 ` David Woodhouse
2002-07-31 11:53 ` Jörn Engel
2003-05-21 11:33 ` Gordon J Milne
2003-05-21 14:18 ` Thayne Harbaugh
2003-05-22 21:57 ` Gordon J Milne
2002-07-31 15:35 ` Stuart Menefy
2002-07-31 20:24 ` Stephen Hui
2002-08-01 10:31 ` David Woodhouse
2002-08-01 18:05 ` Stuart Menefy
2002-08-01 18:26 ` Stuart Menefy [this message]
2002-08-01 19:45 ` Stephen Hui
2002-08-01 22:37 ` Stuart Menefy
2002-08-02 14:46 ` Stephen Hui
2002-08-01 10:35 ` David Woodhouse
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20020801192624.28fe7b7e.stuart.menefy@st.com \
--to=stuart.menefy@st.com \
--cc=linux-mtd@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox