From: "Jeremy Jackson" <jerj@coplanar.net>
To: <linux-mtd@lists.infradead.org>, <linuxbios@lanl.gov>
Subject: jedec_probe_chip error?
Date: Wed, 3 Apr 2002 18:21:02 -0800 [thread overview]
Message-ID: <015501c1db7f$5ea5ac90$7e0aa8c0@bridge> (raw)
in Linux-MTD:
I'm looking at mtd/drivers/chips/jedec_probe.c:jedec_probe_chip
line 794 from current CVS.
for CFI_DEVICETYPE_X8, the unlock1 and unlock2 values
seem wrong. They're currently 0x555 and 0x2aa, resp.
Does it work like this? All of the small (512KiB -
128KiB) devices I've read the datasheets for, require
0x5555 and 0x2aaa here. Are there any devices which
use the current code's values?
Also, I have discovered (see prev. post) at least one device that doesn't
respond to the aa 55 90 sequence, requiring an alternate
"old" sequence instead. Any guidance on the best way to
implement this generically would be appreciated.
Jeremy
next reply other threads:[~2002-04-04 2:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-04 2:21 Jeremy Jackson [this message]
2002-04-04 3:25 ` jedec_probe_chip error? Eric W. Biederman
2002-04-04 10:36 ` Stefan Reinauer
2002-04-05 17:09 ` Richard A. Smith
2002-04-05 18:54 ` Stefan Reinauer
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='015501c1db7f$5ea5ac90$7e0aa8c0@bridge' \
--to=jerj@coplanar.net \
--cc=linux-mtd@lists.infradead.org \
--cc=linuxbios@lanl.gov \
/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