From: Russ.Dill@asu.edu (Russ Dill)
To: linux-mtd@lists.infradead.org
Subject: AMD - Am29LV160B
Date: 03 Mar 2003 18:51:28 -0700 [thread overview]
Message-ID: <1046742660.3368.1.camel@gobbles> (raw)
In-Reply-To: <1046720379.1638.5.camel@gobbles>
On Mon, 2003-03-03 at 12:39, Russ Dill wrote:
> On Mon, 2003-03-03 at 07:08, Amit.Lubovsky at infineon.com wrote:
> > Hi,
> >
> > Has anyone used the mtd device with the AMD
> > Am29LV160B chips? They are 16 Megabit (2M x 8-Bit/1M x 16-Bit) chips
> > and are CFI-compatible.
> >
> > I work with kernel 2.4.6 and am trying to detect 4MB,
> > 2 x16 bit devices in parallel (32 bit access) at address 0,
>
> they work great on my device (as well as the Am29LV800B, which are not
> CFI)
>
> > #define BUSWIDTH 2
>
> I'm away from my code right now, but shouldn't this be 32?
replying to myself here, the correct buswidth for 2 x16 devices in
parallel is 4
next prev parent reply other threads:[~2003-03-04 1:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-03 14:08 AMD - Am29LV160B Amit.Lubovsky at infineon.com
2003-03-03 19:39 ` Russ Dill
2003-03-04 1:51 ` Russ Dill [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-03-04 9:35 Amit.Lubovsky at infineon.com
2003-03-04 10:02 ` Russ Dill
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=1046742660.3368.1.camel@gobbles \
--to=russ.dill@asu.edu \
--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