From: Matthew Locke <mlocke@mvista.com>
To: Frank Przybylski <Frank.Przybylski@vas-gmbh.de>
Cc: "'linuxppc-embedded@lists.linuxppc.org'"
<linuxppc-embedded@lists.linuxppc.org>
Subject: Re: I2C,SPI and QMC
Date: Mon, 07 Aug 2000 10:42:31 -0700 [thread overview]
Message-ID: <398EF507.AA56B9FF@mvista.com> (raw)
In-Reply-To: 398EE632.D9A867E@vas-gmbh.de
Frank Przybylski wrote:
>
> Hi all,
> I plan to use QMC on SCC1 plus SPI on a MPC855T / 860DT for an ISDN BRI
> implementation. I also need I2C for other purposes.
> Following the QMCSUPPLEMENT/AD manual from Motorola I found that one looses
> either I2C using SCC1 for QMC/Ethernet or SPI using SCC2 for QMC/Ethernet.
> I hoped that the I2C/SPI micro code patch would do the trick. But scanning this
> mailing list archive I got aware of troubles with this, or even worse that the
> patch has been removed from the kernel.
> So my question goes like this:
> has anybody managed to use I2C, SPI and QMC on SCC1 altogether, or am I lost
> without any hope?
>
I have successfully used SPI with ethernet on SCC2 with the microcode
patch. However, I did that on a 823, I haven't tried it on the 855/860.
I think I have used the i2c driver with the microcode patch on a 860,
but don't quote me. This was all on the Embedded Planet boards.
Matthew Locke
Montavista Software
http://www.mvista.com
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-08-07 17:42 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 [this message]
2000-08-08 19:27 ` Dan Malek
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=398EF507.AA56B9FF@mvista.com \
--to=mlocke@mvista.com \
--cc=Frank.Przybylski@vas-gmbh.de \
--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).