All of lore.kernel.org
 help / color / mirror / Atom feed
From: Frank Przybylski <Frank.Przybylski@vas-gmbh.de>
To: "'linuxppc-embedded@lists.linuxppc.org'"
	<linuxppc-embedded@lists.linuxppc.org>
Cc: Dan Malek <dan@netx4.com>, Matthew Locke <mlocke@mvista.com>
Subject: Re: I2C,SPI and QMC
Date: Wed, 09 Aug 2000 10:40:29 +0200	[thread overview]
Message-ID: <399118FD.BFE221A3@vas-gmbh.de> (raw)
In-Reply-To: 39905F08.F3E75A26@embeddededge.com


Thank you for your answers. As this is going to be a new hardware I wanted to be
on the secure side. So I'm going to try the patch with the software option on
the very same pins as a fall back option.

    Frank

Dan Malek wrote:
>
> Matthew Locke wrote:
>
> > I have successfully used SPI with ethernet on SCC2 with the microcode
> > patch.
>
> Better than me :-)!  I left my attempt at microcode patches around
> someplace, but was never able to make them work very well.
>
> Depending upon your SPI or I2C requirements, you may just be able to
> toggle the pins in software.  This is all I did.
>
>         -- Dan

--
===============================================================================
Frank Przybylski,VAS GmbH,Gotenstr.6,20097 Hamburg,GERMANY,TEL:+49-40-238568-14
   mailto:Frank.Przybylski@vas-gmbh.de , visit us at http://www.vas-gmbh.de
===============================================================================

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

      reply	other threads:[~2000-08-09  8:40 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-06-09 10:19 Changes in the MPC8xx I2C driver Kim Jørgensen
2000-06-09 17:13 ` Dan Malek
2000-08-07 16:39 ` I2C,SPI and QMC Frank Przybylski
2000-08-07 17:42   ` Matthew Locke
2000-08-08 19:27     ` Dan Malek
2000-08-09  8:40       ` Frank Przybylski [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=399118FD.BFE221A3@vas-gmbh.de \
    --to=frank.przybylski@vas-gmbh.de \
    --cc=dan@netx4.com \
    --cc=linuxppc-embedded@lists.linuxppc.org \
    --cc=mlocke@mvista.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.