From: Dan Malek <dan@netx4.com>
To: Hyun-Joon Cha <tachyon@postech.ac.kr>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: Req. help about SCC2 and SCC3 as ethernet.
Date: Thu, 27 Jul 2000 10:00:36 -0400 [thread overview]
Message-ID: <39804084.5EA8BA01@embeddededge.com> (raw)
In-Reply-To: 01ba01bff79b$9ee78db0$1952df8d@SOYANG
Hyun-Joon Cha wrote:
> After such a success, we removed SCC2 and make SCC3 default ethernet ... then Linux hangs at serial_console_write.
How do you know that is where it stops? With SCC3, you are now
trying to configure Port B, which is also used for the SMC1 configuration.
Perhaps the console and kernel are working fine, and you just messed up
the I/O pins for SMC1.
You will also need to make source code changes to enet.c, as it doesn't
have a standard set of instructions for configuring port B as Ethernet
control/data pins.
-- Dan
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-07-27 14:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-07-27 7:23 Req. help about SCC2 and SCC3 as ethernet Hyun-Joon Cha
2000-07-27 14:00 ` Dan Malek [this message]
2000-07-27 14:38 ` Hyun-Joon Cha
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=39804084.5EA8BA01@embeddededge.com \
--to=dan@netx4.com \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=tachyon@postech.ac.kr \
/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).