From: "Dan Post" <djp.mtd@onemyth.net>
To: "Lothar Wassmann" <LW@KARO-electronics.de>
Cc: linux-mtd@lists.infradead.org
Subject: Re: put_chip() called with oldstate 1!! (linux 2.6.0-rmk2)
Date: Thu, 8 Jan 2004 13:12:06 -0800 [thread overview]
Message-ID: <20040108211206.M17119@onemyth.net> (raw)
In-Reply-To: <16381.14656.474765.390645@ipc1.karo>
On Thu, 8 Jan 2004 12:04:32 +0100, Lothar Wassmann wrote
> I'm using the MTD driver with Intel flash chips on a PXA255 platform
> with Redboot partitions. Whenever I write data to the flash and
> subsequently unmount and remount the modified partition I get several
> messages: 'put_chip() called with oldstate 1!!'.
Hmmm, strange.
Actually, looking at include/linux/mtd/flashchip.h, 1 == FL_STATUS. (That
holds true for older versions as well.)
Looking at the CVS version of cfi_cmdset_0001.c,
chip->state = FL_ERASING;
break;
case FL_READY:
+ case FL_STATUS:
/* We should really make set_vpp() count, rather than doing
this */
DISABLE_VPP(map);
break;
default:
printk(KERN_ERR "put_chip() called with oldstate %d!!\n",
chip->oldstate);
}
Note the line with the "+" at the front. That was added in version 1.127 of
that file (thanks, CVSweb!), on Wed Jul 2 2003, by acurtis.
The comment: "Added FL_STATUS to the FL_READY case in put_chip(). (Eliminate
noise)"
Given my knowledge of flash chips and the driver, that looks like the
appropriate behavior... you may want to upgrade your file or at least add that
line. There have been some other nice changes since then. From a quick
glance, I can't find any mailing list activity from that timeperiod on this
fix though...
Dan
next prev parent reply other threads:[~2004-01-08 21:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-08 11:04 put_chip() called with oldstate 1!! (linux 2.6.0-rmk2) Lothar Wassmann
2004-01-08 21:12 ` Dan Post [this message]
2004-01-09 12:56 ` Lothar Wassmann
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=20040108211206.M17119@onemyth.net \
--to=djp.mtd@onemyth.net \
--cc=LW@KARO-electronics.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox