From: Dan Malek <dan@netx4.com>
To: Matthew Locke <mlocke@mvista.com>
Cc: Frank Przybylski <Frank.Przybylski@vas-gmbh.de>,
"'linuxppc-embedded@lists.linuxppc.org'"
<linuxppc-embedded@lists.linuxppc.org>
Subject: Re: I2C,SPI and QMC
Date: Tue, 08 Aug 2000 15:27:04 -0400 [thread overview]
Message-ID: <39905F08.F3E75A26@embeddededge.com> (raw)
In-Reply-To: 398EF507.AA56B9FF@mvista.com
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
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-08-08 19:27 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 [this message]
2000-08-09 8:40 ` Frank Przybylski
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=39905F08.F3E75A26@embeddededge.com \
--to=dan@netx4.com \
--cc=Frank.Przybylski@vas-gmbh.de \
--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 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).