From: Michel Stempin <michel.stempin@telecom-design.com>
To: linux-mtd@lists.infradead.org
Subject: 8/16/32 bit JEDEC probe
Date: Sat, 13 Sep 2008 00:03:22 +0200 [thread overview]
Message-ID: <1221257002.30016.13.camel@Mikeul> (raw)
Hi list,
I have an interesting case to submit.
I have a SystemBase ARM9 (AT91SAM9260) Eddy-CPU-V2 that can be populated
with either a 32MB SST 39VF3201 (Mfr: 0x00bf, Id: 0x235b) or a 64MB EON
EN29LV640B (Mfr: 0x007f, Id: 0x22cb) part. Mine has the SST part.
As none of these chips were defined in jedec_probe.c, I defined them
there.
However, when the probe is done, an SST 49LF080A (Mfr: 0x00bf, Id:
0x005b) is found instead of my SST 39VF3201...
What is remarkable is that both chips have the same LSB Id!
My conclusion is that the less discriminating 8-bit device detection has
precedence over the more discriminating 16-bit device.
Shouldn't this be the other way around (ie. first detect 32, then 16,
then 8 bit devices)?
If I comment the SST 49LF080A definition, everything works as expected.
Best regards,
--
Michel Stempin
reply other threads:[~2008-09-12 22:15 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1221257002.30016.13.camel@Mikeul \
--to=michel.stempin@telecom-design.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.