linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Jaap-Jan Boor <jjboor@aimsys.nl>
To: Wolfgang Denk <wd@denx.de>
Cc: Kate Alhola <kate@iti.fi>,
	David Jander <david.jander@protonic.nl>,
	linuxppc-embedded@lists.linuxppc.org
Subject: Re: MPX8xx: MMC over SPI....
Date: Wed, 10 Mar 2004 09:32:49 +0100	[thread overview]
Message-ID: <1078907569.16004.9.camel@linpc003.aimsys.nl> (raw)
In-Reply-To: <20040309235955.BC6B7C0655@atlas.denx.de>


Hi,

I agree in this with Wolfgang, I have had very bad experiences
with SPI as inter processor communication channel in the past.
And then you are in the luxury position of having 'intelligence'
(processors) on both sides which can detect and clean up the
CPM's SPI mess.

Jaap-Jan

On Wed, 2004-03-10 at 00:59, Wolfgang Denk wrote:
>
> I don't know your exact application,  but  it  always  gives  me  the
> creeps when I read the phrases "mass storage device" and "SPI bus" in
> the same sentence. I tend to summarize this as follows:
> "mass storage device"  + "SPI bus" = need for redesign :-)
>
> 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
> By the way, ALL software projects are done by iterative  prototyping.
> Some companies call their prototypes "releases", that's all.
>

____
J.G.J. Boor			  Anton Philipsweg 1
Software Engineer		  1223 KZ Hilversum
AimSys bv              		  tel. +31 35 689 1941
Postbus 2194, 1200 CD Hilversum   mailto:jjboor@aimsys.nl


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

  reply	other threads:[~2004-03-10  8:32 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-09 13:18 MPX8xx: MMC over SPI David Jander
2004-03-09 13:41 ` Jaap-Jan Boor
2004-03-09 15:25 ` Wolfgang Denk
2004-03-09 23:23   ` Kate Alhola
2004-03-09 23:59     ` Wolfgang Denk
2004-03-10  8:32       ` Jaap-Jan Boor [this message]
2004-03-13 13:37       ` Kate Alhola
2004-03-14  5:01         ` some LINUX boot-up message loss song sam

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=1078907569.16004.9.camel@linpc003.aimsys.nl \
    --to=jjboor@aimsys.nl \
    --cc=david.jander@protonic.nl \
    --cc=kate@iti.fi \
    --cc=linuxppc-embedded@lists.linuxppc.org \
    --cc=wd@denx.de \
    /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).