From: Manfred Gruber <gruber.m@utanet.at>
To: Linux MTD Mailing List <linux-mtd@lists.infradead.org>
Subject: Number of CFI chips ?
Date: Fri, 20 Aug 2004 13:00:05 +0200 [thread overview]
Message-ID: <200408201300.05579.gruber.m@utanet.at> (raw)
Hi guys !
I am trying to find out why my 2 AM29LV256M do not work.
See before was: Re: JFFS2 with AM29LV256M
I found out that CFI only detects one chip.
What should CFI detect when I have 2 AM29LV256M chips on a 32 bit bus. Each
AM29LV256 has 16 bit bus with with connected to the 32bit bus. So CFI has to
setect 2 chips, am i right ?(wehn interleave is set to 2, and buswith is set
to 32)
When it only detects one chip, my problem must be in detecting the chips by
CFI, is this correct ?
Thanks, regards manfred
next reply other threads:[~2004-08-20 10:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-20 11:00 Manfred Gruber [this message]
2004-08-20 10:57 ` Number of CFI chips ? David Woodhouse
2004-08-20 11:15 ` Manfred Gruber
2004-08-20 11:13 ` David Woodhouse
2004-08-20 11:27 ` Manfred Gruber
2004-08-20 11:40 ` David Woodhouse
2004-08-20 13:23 ` Number of CFI chips and Re: JFFS2 with AM29LV256M Manfred Gruber
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=200408201300.05579.gruber.m@utanet.at \
--to=gruber.m@utanet.at \
--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