From: "LEROY Christophe" <christophe.leroy@c-s.fr>
To: liste ppc embedded <linuxppc-embedded@lists.linuxppc.org>
Cc: TRINH-THAI Florent <florent.trinh-thai@c-s.fr>,
POLI Herve <herve.poli@c-s.fr>,
GUICHARD Michel <michel.guichard@c-s.fr>
Subject: Can we use all SCCs with MPC860
Date: Mon, 16 Dec 2002 10:34:39 +0100 [thread overview]
Message-ID: <3DFD9E2F.CA7417EF@c-s.fr> (raw)
Hello,
I have a board (home made) with a MPC862 running Montavista Linux 2.1
(kernel 2.4.17).
I'd like to use the four SCCs as serial ports, but it seems that only
SCC2 and SCC3 can be configured as serial ports.
Does someone have any idea on how to configure SCC1 and SCC4 as serial
ports also with that kernel ?
Thanks
C. Leroy
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next reply other threads:[~2002-12-16 9:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-16 9:34 LEROY Christophe [this message]
2002-12-16 9:51 ` Can we use all SCCs with MPC860 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=3DFD9E2F.CA7417EF@c-s.fr \
--to=christophe.leroy@c-s.fr \
--cc=florent.trinh-thai@c-s.fr \
--cc=herve.poli@c-s.fr \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=michel.guichard@c-s.fr \
/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).