From: David Woodhouse <dwmw2@infradead.org>
To: "Yuan, Cain" <cain.yuan@intel.com>
Cc: "'linux-mtd@lists.infradead.org'" <linux-mtd@lists.infradead.org>
Subject: Re: JFFS2 peoblems with K3 strata flash on Dalhart
Date: Thu, 08 Aug 2002 09:37:28 +0100 [thread overview]
Message-ID: <31433.1028795848@redhat.com> (raw)
In-Reply-To: <957BD1C2BF3CD411B6C500A0C944CA2601499C38@pdsmsx32.pd.intel.com>
cain.yuan@intel.com said:
> First bootup will success without any error message. but when I reset
> the board and boot it again, many errors occurs.
The error is -EROFS. Your chip might need unlocking each time it's reset. At
least one map driver does this automatically at startup.
The reason the error isn't being reported properly is because I'm
stupid...
--- writev.c 20 May 2002 14:56:39 -0000 1.2
+++ writev.c 8 Aug 2002 08:35:21 -0000 1.3
@@ -7,7 +7,7 @@
*
* For licensing information, see the file 'LICENCE' in this directory.
*
- * $Id: writev.c,v 1.2 2002/05/20 14:56:39 dwmw2 Exp $
+ * $Id: writev.c,v 1.3 2002/08/08 08:35:21 dwmw2 Exp $
*
*/
@@ -28,7 +28,7 @@ static inline int mtd_fake_writev(struct
for (i=0; i<count; i++) {
if (!vecs[i].iov_len)
continue;
- mtd->write(mtd, to, vecs[i].iov_len, &thislen, vecs[i].iov_base);
+ ret = mtd->write(mtd, to, vecs[i].iov_len, &thislen, vecs[i].iov_base);
totlen += thislen;
if (ret || thislen != vecs[i].iov_len)
break;
--
dwmw2
next prev parent reply other threads:[~2002-08-08 8:37 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-07 2:11 JFFS2 peoblems with K3 strata flash on Dalhart Yuan, Cain
2002-08-07 9:46 ` David Woodhouse
2002-08-08 8:37 ` David Woodhouse [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-08-07 15:21 Yuan, Cain
2002-08-07 17:39 ` David Woodhouse
2002-08-07 15:18 Yuan, Cain
2002-08-07 17:42 ` David Woodhouse
2002-08-07 14:28 Gu Susan-w15879
2002-08-07 17:38 ` David Woodhouse
2002-08-07 12:59 Yuan, Cain
2002-08-07 14:20 ` David Woodhouse
2002-08-07 0:19 Yuan, Cain
2002-08-06 5:04 Yuan, Cain
2002-08-06 8:24 ` 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=31433.1028795848@redhat.com \
--to=dwmw2@infradead.org \
--cc=cain.yuan@intel.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