From: "Pichai Raghavan" <ragh_avan@rediffmail.com>
To: linux-mtd@lists.infradead.org
Subject: amd flash problem
Date: 18 Dec 2002 06:56:53 -0000 [thread overview]
Message-ID: <20021218065653.31296.qmail@webmail31.rediffmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 730 bytes --]
Hi All,
I am using the 2.4.2 MTD driver code on my board that has AMD
flash. I am noticing a bug in the write code. AMD flash driver
makes use of unlock bypass mode for doing bulk write; when
issuing
the start and end of the unlock bypass commands;it does not
check
if the flash state is READY.(function cfi_amdstd_write() in
cfi_cmdset_0002.c) In the meanwhile if the flash driver is doing
an erase or write in the context of another process and has got
scheduled out, then the flash gets into a unknown state.
This seems to be causing a problem when write to multiple
partitions are written. Has this problem been fixed in later
kernels? (Had a glance at 2.4.17 code and there also the same
code
is there)
Thanks
Raghav
[-- Attachment #2: Type: message/rfc822, Size: 2163 bytes --]
From: Mail Delivery System <Mailer-Daemon@pentafluge.infradead.org>
To: ragh_avan@rediffmail.com
Subject: Mail delivery failed: returning message to sender
Message-ID: <E18NvQO-0003sx-00@pentafluge.infradead.org>
This message was created automatically by mail delivery software (Exim).
A message that you sent could not be delivered to one or more of its
recipients. This is a permanent error. The following address(es) failed:
lists-mtd@lists.infradead.org
unknown local-part "lists-mtd" in domain "lists.infradead.org"
------ This is a copy of the message, including all the headers. ------
Return-path: <ragh_avan@rediffmail.com>
Received: from webmail31.rediffmail.com ([202.54.124.130] helo=rediffmail.com)
by pentafluge.infradead.org with smtp (Exim 3.22 #1 (Red Hat Linux))
id 18NvQO-0003sv-00
for <lists-mtd@lists.infradead.org>; Mon, 16 Dec 2002 13:36:48 +0000
Received: (qmail 2799 invoked by uid 510); 16 Dec 2002 14:06:31 -0000
Date: 16 Dec 2002 14:06:31 -0000
Message-ID: <20021216140631.2798.qmail@webmail31.rediffmail.com>
Received: from unknown (164.164.83.140) by rediffmail.com via HTTP; 16 dec 2002 14:06:31 -0000
MIME-Version: 1.0
From: "Pichai Raghavan" <ragh_avan@rediffmail.com>
Reply-To: "Pichai Raghavan" <ragh_avan@rediffmail.com>
To: lists-mtd@lists.infradead.org
Subject: AMD CFI driver problem
Content-type: text/plain;
format=flowed
Content-Disposition: inline
Hi All,
I am using the 2.4.2 MTD driver code on my board that has AMD
flash. I am noticing a bug in the write code. AMD flash driver
makes use of unlock bypass mode for doing bulk write; when issuing
the start and end of the unlock bypass commands;it does not check
if the flash state is READY.(function cfi_amdstd_write() in
cfi_cmdset_0002.c) In the meanwhile if the flash driver is doing
an erase or write in the context of another process and has got
scheduled out, then the flash gets into a unknown state.
This seems to be causing a problem when write to multiple
partitions are written. Has this problem been fixed in later
kernels? (Had a glance at 2.4.17 code and there also the same code
is there)
Thanks
Raghav
reply other threads:[~2002-12-18 6:27 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=20021218065653.31296.qmail@webmail31.rediffmail.com \
--to=ragh_avan@rediffmail.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 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.