linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Wolfgang Denk <wd@denx.de>
To: laurent.pinchart@capflow.com
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: Embedded MPC860T & flash memory
Date: Fri, 22 Feb 2002 16:16:48 +0100	[thread overview]
Message-ID: <20020222151653.25BED109E2@denx.denx.de> (raw)
In-Reply-To: Your message of "Fri, 22 Feb 2002 15:26:00 +0100." <3C7654F8.3010801@capflow.com>


Dear Laurent,

in message <3C7654F8.3010801@capflow.com> you wrote:
>
> 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.

For the software it does not matter - both configurations will work.

For the performance it makes a BIG difference.

Go for a buswidth of 32 bits, i. e. use 2 chips in 16 bit mode in
parallel.

Wolfgang Denk

--
Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
Phone: (+49)-8142-4596-87  Fax: (+49)-8142-4596-88  Email: wd@denx.de
"The trouble with doing something right the first time is that nobody
appreciates how difficult it was."                        - Walt West

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2002-02-22 15:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-22 14:26 Embedded MPC860T & flash memory Laurent Pinchart
2002-02-22 15:16 ` Wolfgang Denk [this message]
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=20020222151653.25BED109E2@denx.denx.de \
    --to=wd@denx.de \
    --cc=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).