From: Ricardo Scop <scop@digitel.com.br>
To: "Xiaogeng (Shawn) Jin" <xjin@redswitch.com>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: LXT972 FEC problem on MPC855
Date: Mon, 26 Aug 2002 19:34:24 -0300 [thread overview]
Message-ID: <02082619342400.01116@scop.digitel.com.br> (raw)
In-Reply-To: <3D6A9E57.1060308@redswitch.com>
Shawn:
Maybe I have a contribution...
On Monday 26 August 2002 18:32, Xiaogeng (Shawn) Jin wrote:
> > You are passing bad/insufficient boot arguments to the Linux kernel;
> > unfortunaltely you don;t show us this part of the boot messages, so I
> > cannot even guess what you're doing wrong.
>
> Finally I figured out the problem and solved it. The problem is that the
> kernel didn't get the LINK status correctly. The 'fep->link' was always
> 0 which means the link is down or autonegotiation is in progress.
>
> In the code which defines 'phy_info_lxt971', it says that somehow LXT971
> tells me that the link is down when the first read after power-up. So
> you have to read MII_REG_SR to set 'fep->phy_status' accordingly. But in
> my case, the read action occurred too early to wait till the link is up.
> So what I did is to delay 5s before reading MII_REG_SR during opening
> FEC device. I guess it takes the link a while to autonegotiate the speed.
Hmm. I suppose PHY should interrupt when link status change, and therefore
phy_status would be updated accordingly. So, maybe you have a problem with
your board's PHY interrupt signal.
Hope this helps.
-Scop.
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2002-08-26 22:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-26 1:20 LXT972 FEC problem on MPC855 Xiaogeng (Shawn) Jin
2002-08-26 18:04 ` 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 [this message]
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=02082619342400.01116@scop.digitel.com.br \
--to=scop@digitel.com.br \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=xjin@redswitch.com \
/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).