linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Stephan Linke" <Stephan.Linke@epygi.de>
To: "Linuxppc-Embedded" <linuxppc-embedded@lists.linuxppc.org>
Subject: running 8xx without UART
Date: Thu, 12 Jun 2003 09:34:08 +0200	[thread overview]
Message-ID: <FCEAKDJJAPHPLJFINDAJAEHGDCAA.Stephan.Linke@epygi.de> (raw)


Hi,

is it possible to make a 8xx kernel without setting up one of the serial interfaces for UART mode? It seames to me like it is only
possible to choose between the CPM interfaces.
We are experiencing problems with SCC3 running ethernet and SMC1 as console interface on a 852.

Thanx, Stephan


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

             reply	other threads:[~2003-06-12  7:34 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-12  7:34 Stephan Linke [this message]
2003-06-12 10:04 ` running 8xx without UART Wolfgang Denk
2003-06-12 10:19   ` Pantelis Antoniou
2003-06-12 10:37     ` Wolfgang Denk
     [not found] <FCEAKDJJAPHPLJFINDAJCEHLDCAA.Stephan.Linke@epygi.de>
2003-06-13  6:52 ` Stephan Linke

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=FCEAKDJJAPHPLJFINDAJAEHGDCAA.Stephan.Linke@epygi.de \
    --to=stephan.linke@epygi.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).