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: Wed, 07 Aug 2002 10:46:49 +0100 [thread overview]
Message-ID: <30833.1028713609@redhat.com> (raw)
In-Reply-To: <957BD1C2BF3CD411B6C500A0C944CA2601499C38@pdsmsx32.pd.intel.com>
cain.yuan@intel.com said:
> According to your email I rebuild a JFFS2 image with the block
> size 0x10000, same as the datasheet saids. but the problem still
> exist. First bootup will success without any error message. but when
> I reset the board and boot it again, many errors occurs.
Looks like you should be using 0x20000. 0x10000 is fine but triggers
harmless messages about 'Empty block at 0x.... '. I think you were using
0x40000 before which would have caused problems.
The other problem still remains, and isn't related, though...
> Write of 68 bytes at 0x0035e908 failed. returned 0, retlen 0
> Not marking the space at 0x0035e908 as dirty because the flash driver returned retlen zero
The hardware driver seems broken -- it's returning success but not actually
reporting that it's written any data. What driver, what version?
--
dwmw2
next prev parent reply other threads:[~2002-08-07 9:46 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 [this message]
2002-08-08 8:37 ` David Woodhouse
-- 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=30833.1028713609@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