linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Xiaogeng (Shawn) Jin" <xjin@redswitch.com>
To: Ricardo Scop <scop@digitel.com.br>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: LXT972 FEC problem on MPC855
Date: Tue, 27 Aug 2002 17:19:31 -0700	[thread overview]
Message-ID: <3D6C1713.2050802@redswitch.com> (raw)
In-Reply-To: 02082619342400.01116@scop.digitel.com.br


>>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.

Yeah, I think so. So I have to check whether the PHY interrupt is
enabled or not. Thanks for your thoughts.

- Shawn.


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

      reply	other threads:[~2002-08-28  0:19 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
2002-08-28  0:19         ` Xiaogeng (Shawn) Jin [this message]

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=3D6C1713.2050802@redswitch.com \
    --to=xjin@redswitch.com \
    --cc=linuxppc-embedded@lists.linuxppc.org \
    --cc=scop@digitel.com.br \
    /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).