linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Wolfgang Denk <wd@denx.de>
To: David Jander <david.jander@protonic.nl>
Cc: "Frank Robbins" <Frank.Robbins@Analogue-Micro.com>,
	linuxppc-embedded@lists.linuxppc.org
Subject: Re: Support for MPC852T, any experience ?
Date: Thu, 19 Jun 2003 12:23:11 +0200	[thread overview]
Message-ID: <20030619102316.10689C5FD7@atlas.denx.de> (raw)
In-Reply-To: Your message of "Thu, 19 Jun 2003 11:06:38 +0200." <200306191106.39116.david.jander@protonic.nl>


Dear David,

in message <200306191106.39116.david.jander@protonic.nl> you wrote:
>
> Great ! Have you had much trouble making all the hardware work, or do all the
> existing drivers in arch/ppc/8xx_io work out of the box ?

They should work out of the box. This is just another member  of  the
8xx family.

> Equiped with a MMC slot (for MMC's in SPI mode over the SPI interface),

Are you sure you really want to do this? Please be aware that the SPI
port on the 8xx was NOT designed for high performance /  volume  data
transfers. Motorola writes:

        The SPI was not designed to be a high-bandwidth channel. It
        can run very quickly for bursts of up to 16-bits. But the
        peripheral has no FIFO and low priority in the MPC860 and
        thus you cannot burst lots of data quickly through the
        interface.
	...
        Note that the SPI is of lower priority internally than the
        SCCs, thus, the SPI will be the first device to be "starved".
        Snce it has no FIFO, it is especially sensitive to underruns.
        The best way to prevent this is to use a buffer size of 1
        "character" (of size programmed in the mode register).
        ...

Also, you should be aware that the SPI  protocol  is  implemented  as
microcode  running  on the CPM, so any high-speed data transfers will
suck up CPM performance.


>From my experience SPI on the 8xx should NOT be used  for  mass  data
transfers. You will run into a LOT of problems. Been there ...


> 16-64Mb SDRAM, 2-8Mb Flash (for kernel, bootloader, some basic rootfs, data
> storage) and the applications mostly on a fs on MMC.

You mean a filesystem on a device over SPI? I _strongly_ recommend to
change your design. You will run into _serious_ trouble that way.


> I am specially interested in hearing about experience with using a filesystem
> on a MMC via the SPI interface.

See above. Don't even think about it.




Best regards,

Wolfgang Denk

--
Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
Phone: (+49)-8142-4596-87  Fax: (+49)-8142-4596-88  Email: wd@denx.de
Another megabytes the dust.

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

      reply	other threads:[~2003-06-19 10:23 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-17 11:14 Support for MPC852T, any experience ? David Jander
2003-06-17 11:27 ` Wolfgang Denk
2003-06-18 12:14 ` Frank Robbins
2003-06-19  9:06   ` David Jander
2003-06-19 10:23     ` Wolfgang Denk [this message]

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=20030619102316.10689C5FD7@atlas.denx.de \
    --to=wd@denx.de \
    --cc=Frank.Robbins@Analogue-Micro.com \
    --cc=david.jander@protonic.nl \
    --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).