From: Axel Ludszuweit <alu@keymile.com>
To: linux-mtd@lists.infradead.org
Subject: cfi_amdstd_resume vs. cfi_intelext_resume
Date: Thu, 08 Jan 2004 08:33:53 +0100 [thread overview]
Message-ID: <3FFD07E1.2040305@keymile.com> (raw)
Hello,
I have compared both function, mentioned in the subject.
I think, there is an error in
static void cfi_intelext_resume(struct mtd_info *mtd),
which can be fixed with the following patch.
--- ./drivers/mtd/chips/cfi_cmdset_0001.c.orig 2004-01-08 08:28:23.000000000 +0100
+++ ./drivers/mtd/chips/cfi_cmdset_0001.c 2004-01-08 08:29:29.000000000 +0100
@@ -1676,7 +1676,7 @@
/* Go to known state. Chip may have been power cycled */
if (chip->state == FL_PM_SUSPENDED) {
- cfi_write(map, CMD(0xFF), 0);
+ cfi_write(map, CMD(0xFF), chip->start);
chip->state = FL_READY;
wake_up(&chip->wq);
}
Is this correct, or have I misunderstanding something?
--
--------------------------------------------
Axel Ludszuweit
Keymile GmbH
Wohlenbergstr. 3, D-30179 Hannover
Tel.: +49 511 / 978197-630
Fax : +49 511 / 978197-670
http://www.keymile.com
mailto:axel.ludszuweit@keymile.com
>> Be the FIRST on the LAST MILE <<
reply other threads:[~2004-01-08 7:36 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=3FFD07E1.2040305@keymile.com \
--to=alu@keymile.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