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 15:20:10 +0100 [thread overview]
Message-ID: <24862.1028730010@redhat.com> (raw)
In-Reply-To: <957BD1C2BF3CD411B6C500A0C944CA2601499C3B@pdsmsx32.pd.intel.com>
cain.yuan@intel.com said:
> --- Since using CFI with Ks flash, I think it is CFI driver and
> cfi_cmdset_001.c, the code reside in linux2.4.18-rmk6-pxa2.
> Should I download newest code from CVS server and merge them
> into the kernel src tree?
Er, I don't think there have been significant changes since then. Updating
to the latest code certainly can't hurt though.
The problem is that the chip write() call is returning zero (i.e. no error)
but is setting the number of written bytes to zero. That doesn't make sense
-- if it didn't write all the bytes we asked it to, then there must have
been an error.
This chip supports buffer writes, doesn't it? Can you add some extra
'printk' calls in cfi_intelext_write_buffers() to try to show what's
happening to 'retlen' and when it returns.
--
dwmw2
next prev parent reply other threads:[~2002-08-07 14:20 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-07 12:59 JFFS2 peoblems with K3 strata flash on Dalhart Yuan, Cain
2002-08-07 14:20 ` 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 2:11 Yuan, Cain
2002-08-07 9:46 ` David Woodhouse
2002-08-08 8:37 ` 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=24862.1028730010@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