From: Steven Scholz <steven.scholz@imc-berlin.de>
Cc: "'linux-mtd@lists.infradead.org'" <linux-mtd@lists.infradead.org>
Subject: Re: kernel oops in cfi_cmdset_0002.c:do_write_one()...
Date: Thu, 08 Apr 2004 09:16:13 +0200 [thread overview]
Message-ID: <4074FC3D.1030708@imc-berlin.de> (raw)
In-Reply-To: <1081354787.4799.191.camel@tubarao>
Thayne Harbaugh wrote:
> On Wed, 2004-04-07 at 09:43, Steven Scholz wrote:
>
>>Hi there,
>>
>>on my embedded PPC system with linux-2.425 I have two flash devices.
>
>
>>Warning: DQ5 raised while program operation was in progress, however operation completed OK
>>Warning: DQ5 raised while program operation was in progress, however operation completed OK
>>Warning: DQ5 raised while program operation was in progress, however operation completed OK
>>Waiting for write to complete timed out in do_write_oneword.
>
>
> These error messages are from an ancient version of cfi_cmdset_0002.c.
> They come from over-efficient software design that didn't consider the
> quirks of how a flash chip works. Have you tried a recent version?
Ehm. I am using a 2.4.25 kernel. I thought the MTD code in there should be
quiet recent...
How can I check the version of the MTD code in my kernel tree?
--
Steven Scholz
imc Measurement & Control imc Meßsysteme GmbH
Voltastr. 5 Voltastr. 5
13355 Berlin 13355 Berlin
Germany Deutschland
next prev parent reply other threads:[~2004-04-08 7:16 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-07 15:43 kernel oops in cfi_cmdset_0002.c:do_write_one() Steven Scholz
2004-04-07 16:19 ` Thayne Harbaugh
2004-04-07 16:47 ` David Vrabel
2004-04-11 11:40 ` Steven Scholz
2004-04-08 7:16 ` Steven Scholz [this message]
2004-04-08 13:29 ` Steven Scholz
2004-04-08 14:37 ` Jörn Engel
2004-04-08 19:28 ` Thomas Gleixner
2004-04-08 19:47 ` Jörn Engel
2004-04-09 12:42 ` David Woodhouse
2004-04-13 9:31 ` Jörn Engel
2004-04-13 14:28 ` David Woodhouse
2004-04-13 11:04 ` David Vrabel
[not found] <D73A25AA6E54D511AD74009027B1110F5BB16A@ORION>
2004-04-07 16:12 ` Steven Scholz
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=4074FC3D.1030708@imc-berlin.de \
--to=steven.scholz@imc-berlin.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.