From: Artem Bityutskiy <dedekind@infradead.org>
To: Niels Gram Jeppesen <ngj@danelec-marine.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: chip_ready patch for SST39VF640xB
Date: Sun, 04 Feb 2007 11:51:39 +0200 [thread overview]
Message-ID: <1170582699.3628.33.camel@sauron> (raw)
In-Reply-To: <4F576438CB468649B9FD55650B93FA238DB4A1@bes01.blokken.lan>
Hi,
On Fri, 2007-02-02 at 17:03 +0100, Niels Gram Jeppesen wrote:
> In cfi_cmdset_0002.c, chip_ready seems to be unreliable on the SST39VF640xB chip. The attached patch add two extra reads to chip_ready in accordance with the chip data sheet (page 3, "Write Operation Status Detection"). This seems to make the write cycle completion detection reliable. I have not tested the patch on any other chips but I would think that it would be harmless on chips that do not need the extra reads.
1. The patch is not applicable to mtd-2.6.git.
2. Please, add Siged-off-by line.
Look here please: http://www.linux-mtd.infradead.org/source.html
--
Best regards,
Artem Bityutskiy (Битюцкий Артём)
prev parent reply other threads:[~2007-02-04 9:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-02 16:03 chip_ready patch for SST39VF640xB Niels Gram Jeppesen
2007-02-04 9:51 ` Artem Bityutskiy [this message]
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=1170582699.3628.33.camel@sauron \
--to=dedekind@infradead.org \
--cc=linux-mtd@lists.infradead.org \
--cc=ngj@danelec-marine.com \
/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