From: "Xiaogeng (Shawn) Jin" <xjin@redswitch.com>
To: linuxppc-embedded@lists.linuxppc.org
Subject: LXT972 FEC problem on MPC855
Date: Sun, 25 Aug 2002 18:20:42 -0700 [thread overview]
Message-ID: <3D69826A.6020504@redswitch.com> (raw)
Hi,
After running ppcboot on our board successfully (including the fast
ethernet LXT972), we have trouble on enabling FEC on linux kernel. The
problem is that we cannot send any packets through the network after the
kernel is booted. The ethernet looks OK during initialization according
to the printed messages. We are trying to locate the problem but haven't
found yet so far. Any hints on what caused such problem?
My configuration on kernel (linux-2.4.4-08-09 from DENX) is
860T FEC Ethernet
Use MDIO for PHY configuration
Support LXT971 PHY
Thanks.
- Shawn.
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next reply other threads:[~2002-08-26 1:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-26 1:20 Xiaogeng (Shawn) Jin [this message]
2002-08-26 18:04 ` LXT972 FEC problem on MPC855 Xiaogeng (Shawn) Jin
2002-08-26 18:27 ` Wolfgang Denk
2002-08-26 19:17 ` Xiaogeng (Shawn) Jin
[not found] ` <3D6A9E57.1060308@redswitch.com>
2002-08-26 22:34 ` Ricardo Scop
2002-08-28 0:19 ` Xiaogeng (Shawn) Jin
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=3D69826A.6020504@redswitch.com \
--to=xjin@redswitch.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).