public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: "Brian T" <btuch@usa.net>
To: "Brian T" <btuch@usa.net>, <linux-mtd@lists.infradead.org>
Subject: Re: Intel 28F128 - Linux-2.4.24 broke jffs2 v2.2?
Date: Wed, 18 Feb 2004 09:05:53 -0600	[thread overview]
Message-ID: <01f101c3f630$b47b04d0$fd0ba8c0@briantpc> (raw)
In-Reply-To: 01c701c3f62c$d88fc300$fd0ba8c0@briantpc

[-- Attachment #1: Type: text/plain, Size: 481 bytes --]


>
> I found the problem, and the attached patch fixed it for me.  Not sure if

Sorry, forgot the diff attachment.

> this is the correct way to fix this though.  I took a line from
> jedec_probe.c and added it to cfi_util.c to get the Micron chip into the
> right mode. Micron requires the 0xFF (according to the specs) as do some
> Intel chips.
>
> Comments? If this is valid can it be added to CVS? If not, does someone
know
> the proper way of doing it?
>
> Thanks,
>
> -Brian

[-- Attachment #2: cfi_util.c.diff --]
[-- Type: application/octet-stream, Size: 756 bytes --]

nux-2.4.x/drivers/mtd/chips/cfi_util.c.orig       Tue Feb 17 15:32:24 2004
+++ linux-2.4.x/drivers/mtd/chips/cfi_util.c    Tue Feb 17 16:33:03 2004
@@ -68,6 +68,14 @@
        /* Make sure it's in read mode */
        cfi_send_gen_cmd(0xf0, 0, base, map, cfi, cfi->device_type, NULL);
 
+        /* Some misdesigned intel chips do not respond for 0xF0 for a reset,
+         * so ensure we're in read mode.  Send both the Intel and the AMD command
+         * for this.  Intel uses 0xff for this, AMD uses 0xff for NOP, so
+         * this should be safe. ALSO Some Intel's Specify 0xFF, and Micron
+        * REQUIRES it.
+         */
+        cfi_send_gen_cmd(0xFF, 0, base, map, cfi, cfi->device_type, NULL);
+
        return extp;
 }
 

      reply	other threads:[~2004-02-18 15:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-16 22:36 Intel 28F128 - Linux-2.4.24 broke jffs2 v2.2? Brian T
2004-02-17 20:20 ` Brian T
2004-02-18 14:38   ` Brian T
2004-02-18 15:05     ` Brian T [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='01f101c3f630$b47b04d0$fd0ba8c0@briantpc' \
    --to=btuch@usa.net \
    --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