linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Wolfgang Denk <wd@denx.de>
To: laurent.pinchart@capflow.com
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: SCC or SMC for console ?
Date: Thu, 14 Feb 2002 19:31:58 +0100	[thread overview]
Message-ID: <20020214183203.C4651109E2@denx.denx.de> (raw)
In-Reply-To: Your message of "Thu, 14 Feb 2002 18:28:17 +0100." <3C6BF3B1.2040906@capflow.com>


Dear Laurent,

in message <3C6BF3B1.2040906@capflow.com> you wrote:
>
> I need 4 serial ports at runtime, and was wondering if I should rather
> use 2SMC + 2SCC or 4 SCC (or 1SMC + 3SCC).

Assuming that you need Ethernet: if you can use the FEC for Ethernet,
that it does not matter much; otherwise I'd recommend to use  2SMC  +
2SCC  or  1SMC  +  3SCC  so  that  you  have at east one SCC left for
Ethernet.

> I need a console, but no hardware flow control (which would force the
> use of SCC).

Should be no problem. The kernel on our FTP server was tested with  6
serial  ports  on  a  MPC860, with HW flow controll on all SCC's. The
only problem in such a configuration is that you have only 4 BRG's so
two ports have to share the baudrate with another port.

Wolfgang Denk

--
Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
Phone: (+49)-8142-4596-87  Fax: (+49)-8142-4596-88  Email: wd@denx.de
See us @ Embedded Systems Nuremberg, Feb 19-21, Hall 12 K01 (with TQ)

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

  parent reply	other threads:[~2002-02-14 18:31 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-14 17:28 SCC or SMC for console ? Laurent Pinchart
2002-02-14 18:16 ` Dan Malek
2002-02-15 13:10   ` Laurent Pinchart
2002-02-14 18:31 ` Wolfgang Denk [this message]
2002-02-15 14:24   ` Laurent Pinchart
2002-02-15 14:35     ` Wolfgang Denk

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=20020214183203.C4651109E2@denx.denx.de \
    --to=wd@denx.de \
    --cc=laurent.pinchart@capflow.com \
    --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).