From: Bill Gatliff <bgat@billgatliff.com>
To: linux-mtd@lists.infradead.org
Subject: Re: Intel flash and cfi_probe.c
Date: Tue, 20 Jan 2004 19:32:20 -0600 [thread overview]
Message-ID: <400DD6A4.6040903@billgatliff.com> (raw)
In-Reply-To: <1074638670.16045.74.camel@imladris.demon.co.uk>
David:
I had seen the lines of code that Thayne had referred to; there are
other exit paths out of that code that leave the flash in READ STATUS
mode, apparently. Haven't researched it enough yet.
Let me know what, if anything, I can do to help!
b.g.
David Woodhouse wrote:
>On Tue, 2004-01-20 at 13:50 -0800, Dan Post wrote:
>
>
>>Hi,
>>
>>I was looking at the cfi_probe.c file, and noticed that there are numerous
>>'0xF0' commands to flash (theoretically to put the flash back into read array
>>mode). This is incorrect in terms of Intel flash; according to the datasheets
>>for L18/30 and K3/18, the "read array" command is 0xFF.
>>
>>
>
>Yeah.... the CFI spec says how to get into query mode, but unfortunately
>doesn't specify how to get out of it. And without getting out of it we
>can't check for aliases.
>
>We'd previously observed that 0xF0 happened to work for Intel chips...
>now evidently it doesn't any more. I suspect we might just have to bite
>the bullet and make it depend on the chip type, although it was easier
>to avoid that.
>
>
>
>>What would happen if we issued an 0xF0;0xFF to an AMD chip? Or 0xFF;0xF0?
>>Any AMD chip-heads care to answer? It looks like it will "work" on Intel chips...
>>
>>
>
>Hmmm. That could work.
>
>
>
--
Bill Gatliff
Embedded GNU, Linux, and other board support packages.
bgat@billgatliff.com
next prev parent reply other threads:[~2004-01-21 1:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-20 21:50 Intel flash and cfi_probe.c Dan Post
2004-01-20 22:40 ` Thayne Harbaugh
2004-01-20 22:44 ` David Woodhouse
2004-01-21 1:32 ` Bill Gatliff [this message]
2004-01-21 1:29 ` Bill Gatliff
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=400DD6A4.6040903@billgatliff.com \
--to=bgat@billgatliff.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