LinuxPPC-Dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: acurtis@onz.com
To: BlakesleeS@embeddedplanet.com
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: scc1 on an mpc8260
Date: Mon, 16 Sep 2002 15:53:57 -0700 (PDT)	[thread overview]
Message-ID: <20020916155357.17425.h002.c007.wm@mail.directvinternet.com.criticalpath.net> (raw)


> Does anybody know of a problem with using SCC1 on an mpc8260?  Any advice
> would be appreciated.

We are using all the SMC/SCC devices. What exactly is your concern?

------------------------------------------------------------
Allen Curtis              |  All good things come to those
Ones and Zeros, Inc.      |  who wait. Some of us have to
mailto:acurtis@onz.com    |  wait a little longer.

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

             reply	other threads:[~2002-09-16 22:53 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-16 22:53 acurtis [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-09-16 20:41 scc1 on an mpc8260 Steven Blakeslee

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=20020916155357.17425.h002.c007.wm@mail.directvinternet.com.criticalpath.net \
    --to=acurtis@onz.com \
    --cc=BlakesleeS@embeddedplanet.com \
    --cc=linuxppc-dev@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