From: Steve Wahl <steve.wahl@qlogic.com>
To: linux-mtd@lists.infradead.org
Subject: jedec_probe.c bug: AMD AM29LV800 in byte mode
Date: Tue, 8 Mar 2005 13:08:53 -0600 [thread overview]
Message-ID: <20050308190853.GA18903@qlogic.com> (raw)
[Trying again, maybe I was overbose last time. :-) If I missed a
response, feel free to bash me with a clue-by-4.]
When this chip (AM29LV800) is in byte mode, the id should be read from
location 2, and when in word mode, the id should be read from location
1.
jedec_read_id() (jedec_probe.c, near line 1675) seems to do the exact
opposite (read from 2 in word mode, and 1 in byte mode). Because of
this, it is not finding this chip for me.
I hacked it to always read from 2 rather than 1.
I'm willing to develop a patch for this, but I'm sure some chips
actually work with the current code, and I don't want to break them.
So I need some guidance on how to proceed.
Should I be reading both location 1 and location 2, and add a field to
jedec_table[] that indicates which location(s) to compare with?
--> Steve Wahl, Qlogic Corporation
next reply other threads:[~2005-03-08 19:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-08 19:08 Steve Wahl [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-02-18 16:48 jedec_probe.c bug: AMD AM29LV800 in byte mode Steve Wahl
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=20050308190853.GA18903@qlogic.com \
--to=steve.wahl@qlogic.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