From: Laurent Pinchart <laurent.pinchart@capflow.com>
To: linuxppc-embedded@lists.linuxppc.org
Subject: Embedded MPC860T & flash memory
Date: Fri, 22 Feb 2002 15:26:00 +0100 [thread overview]
Message-ID: <3C7654F8.3010801@capflow.com> (raw)
Hi everybody,
I'm developping a custom MPC860T board, and need 16MB of flash memory.
As I need to be able to write to the memory using the MTD layer, I was
wondering if it would be better to use 2 16-bit wide chips in
interleaved mode on a 32-bit bus (connecting them in parallel to the
bus, one of them storing D[0:15] and the other one D[16:31]), or to use
them in non-interleaved mode (non-overlapping address ranges) on a
16-bit bus. It seems that the Linux MTD layer can support both
configurations, but I don't have a deep knowledge of that code, and thus
would appreciate any advice.
I'll probably use AMD devices.
Thanks in advance for your help.
Laurent Pinchart
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next reply other threads:[~2002-02-22 14:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-22 14:26 Laurent Pinchart [this message]
2002-02-22 15:16 ` Embedded MPC860T & flash memory Wolfgang Denk
2002-02-25 17:15 ` Laurent Pinchart
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=3C7654F8.3010801@capflow.com \
--to=laurent.pinchart@capflow.com \
--cc=linuxppc-embedded@lists.linuxppc.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;
as well as URLs for NNTP newsgroup(s).